Oops, sorry, I didn't read your bar/baz correctly. Yes, it's two directory
objects, but it's only one file object, and the history (not including the
name changes) is attached to the file object, not the directory object. This
is implemented via an object id for each file object, something like an inode
> > > > ...then this part gets much easier.
> > >
> > > ... by screwing it up. This is exactly one of the problems noted for
> > > CVS.
> > CVS doesn't have directory objects.
> And it doesn't keep history across moves, as the only way it knows to move
> a file is destroying the original and creating a fresh copy.
Ah, but it does. Sorry for not explaining the object id thing earlier.
> > Does anybody have a convenient mailing list for this design discussion?
> Good idea to move this off LKML
Yup, but nobody has offered one yet, so...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/