[darcs-devel] [issue1039] wish: detect seemingly unrelated repositories

[Eric Kow]

Eric Kow <kowey at darcs.net> added the comment:

For what it's worth, I find Jason's token based approach to be simpler and more
predictable (from the user's point of view).

I was thinking that we do not have to make any guarantees about the repository
identifier; it could just be a text file (say _darcs/repo-id) that can be
created, modified, deleted by the user with no ill effects. To be helpful, darcs
could create a default token for you when you init.

What I like about the id approach is that the user has control over the whole
process.  You want to make this repo have the same id has the other one, fine,
just copy the ancestry token.  The only stumbling block is that users may not
realise how simple, stupid (this is a compliment) and flexible the approach is.
   But maybe that can be solved with documentation or a UI message, like

"If you want darcs to treat this repository as related, just copy the
_darcs/repo-id file"

(Here we are conspicuously NOT doing it for the user so as to de-mystify the
approach)

__________________________________
Darcs bug tracker <bugs at darcs.net>
<http://bugs.darcs.net/issue1039>
__________________________________