On Wed, May 11, 2005 at 06:13:45PM -0700, H. Peter Anvin wrote:
Count me in the "what does repoid help?" camp. If we create a
new UUID on each clone, imagine this typical usage:
linux-2.6.git has repoid AAAAAA.
I clone it locally, local-2.6-clean, repoid BBBBBB
I clone the local one, local-2.6-working, repoid CCCCCC
I work in the local one and commit my change. commit abcd,
repoid CCCCCC.
I then rsync, copy, or clone that working repository to some
place that Linus can pull from.
I then throw away the copy with repoid CCCCCC, because I'm done
with that temporary work area.
lather, rinse, repeat.
IOW, each of my changes, if I work like this, has a different
repoid. And when a problem arises, the repoid tells us diddly. I
thought one of the tenents of bk/git/codeville/whatever development is
that clone is the way to do any temporary area. You work in a clone or
10, and then clean up for submission. Which of the 10 clones is the
associated repoid seems, well, unimporant.
Joel