Question about hard links on Linux

Hi,

I found following article in infocenter.

http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.team.connector.scm.cc.doc/topics/t_import_paths.html

----------------------------------------------------------------------------------------------------------------------
Restriction:
Unlike Rational ClearCase, Rational Team Concert source control does
not support hard links.
If multiple hard links to the same file are encountered during an
import,
only one link target (the final one encountered during the import)
remains
in the synchronized stream after the import completes.

Note:
If you are using Rational Team Concert version 2.0.0.2 or later,
symbolic links are supported.
The ClearCase Synchronizer and Importer create Jazz symbolic links for
any ClearCase symbolic links that are imported.
Likewise, the Synchronizer creates ClearCase symbolic links for any
Jazz symbolic links that are exported.
Symbolic links can only be loaded from a repository workspace on a
platform that supports symbolic links.
----------------------------------------------------------------------------------------------------------------------


The article means hard links are not supported yet right?
And if we use hard links on RTC itself(we don't use ClearCase at all),
what problems are considered to happen?


Regards
James

If you put a file with multiple hard links under source control, I
predict that each hardlink'ed location will get its own (separate)
version-controlled file. But I'm currently running on a Windows box
that does not support hard links, so I can't verify that.

One interesting question is the behavior when you modify a file that is
hard-linked into multiple version-controlled folders. Does pending
changes show an "unresolved" file at both hardlink locations, or just
one? If only at one, what happens when you select the "refresh"
operation on the file that is not showing modifications.

Cheers,
Geoff

On 10/6/2010 5:08 AM, JamesLa wrote:

Hi,

I found following article in infocenter.

http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.team.connector.scm.cc.doc/topics/t_import_paths.html

----------------------------------------------------------------------------------------------------------------------
Restriction:
Unlike Rational ClearCase, Rational Team Concert source control does
not support hard links.
If multiple hard links to the same file are encountered during an
import,
only one link target (the final one encountered during the import)
remains
in the synchronized stream after the import completes.

Note:
If you are using Rational Team Concert version 2.0.0.2 or later,
symbolic links are supported.
The ClearCase Synchronizer and Importer create Jazz symbolic links for
any ClearCase symbolic links that are imported.
Likewise, the Synchronizer creates ClearCase symbolic links for any
Jazz symbolic links that are exported.
Symbolic links can only be loaded from a repository workspace on a
platform that supports symbolic links.
----------------------------------------------------------------------------------------------------------------------


The article means hard links are not supported yet right?
And if we use hard links on RTC itself(we don't use ClearCase at all),
what problems are considered to happen?


Regards
James

Hi Geoff

Thank you for your answer.
I will try it.

And let me ask one more questoin(Just a curious).

On Windows client.
Is Windows short cut supported as well as symbolic links?
If you know about it, please let me know.


Regards
James


gmclemmwrote:
If you put a file with multiple hard links under source control, I
predict that each hardlink'ed location will get its own (separate)
version-controlled file. But I'm currently running on a Windows box

that does not support hard links, so I can't verify that.

One interesting question is the behavior when you modify a file that
is
hard-linked into multiple version-controlled folders. Does pending

changes show an "unresolved" file at both hardlink
locations, or just
one? If only at one, what happens when you select the
"refresh"
operation on the file that is not showing modifications.

Cheers,
Geoff

On 10/6/2010 5:08 AM, JamesLa wrote:
Hi,

I found following article in infocenter.


http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.team.connector.scm.cc.doc/topics/t_import_paths.html


----------------------------------------------------------------------------------------------------------------------
Restriction:
Unlike Rational ClearCase, Rational Team Concert source control
does
not support hard links.
If multiple hard links to the same file are encountered during an
import,
only one link target (the final one encountered during the import)
remains
in the synchronized stream after the import completes.

Note:
If you are using Rational Team Concert version 2.0.0.2 or later,
symbolic links are supported.
The ClearCase Synchronizer and Importer create Jazz symbolic links
for
any ClearCase symbolic links that are imported.
Likewise, the Synchronizer creates ClearCase symbolic links for any
Jazz symbolic links that are exported.
Symbolic links can only be loaded from a repository workspace on a
platform that supports symbolic links.

----------------------------------------------------------------------------------------------------------------------


The article means hard links are not supported yet right?
And if we use hard links on RTC itself(we don't use ClearCase at
all),
what problems are considered to happen?


Regards
James