Hi,
On 9 Mar 2003, Eric W. Biederman wrote:
> > This is actually a key feature I want to see in a SCM system - the ability
> > to keep multiple developments within the same repository. I want to pull
> > other source tress into a branch and compare them with other branches and
> > merge them into new branches.
>
> In a distributed system everything happens on a branch.
That's true, but with bk you have to use separate directories for that,
which makes cross references between branches more difficult.
> > I agree, what I was trying to say is that the SCCS format makes a few
> > things more complex than they had to be.
>
> I don't know, if the problem really changes that much. How do
> you pick a globally unique inode number for a file? And then
> how do you reconcile this when people on 2 different branches create
> the same file and want to merge their versions together?
Unique identifier are needed for change sets anyway and if you decide
during merge, that two files are identical, at least one branch has to
carry the information that these identifiers point to the same file.
> So as a very rough approximation.
> - Distribution is the problem.
I would rather say, that it's only one (although very important) problem.
bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Mar 15 2003 - 22:00:18 EST