[snip]
> and the way that people currently think (and thus speak) of these
> things, saying that you're using a version 'e' kernel is ambiguous
> because it may or may not have 'c' or 'd'. This ambiguity also
> complicates the task of reproducing a tree at some known state later.
Well, this is what tags are for. The ambiguity in changesets is OK,
since it's possible anyhow with multiple people (and with some creative
work maybe, 'c' would be before 'd', but at the same level, so 'c'
wouldn't get 'd', but this might break the new behavior so..) But if
you do:
a b (tag v1) c e (tag v2)
d
f (added after the v2 tag)
it should be possible to have the 'v2' tag say what changsets it had, or
even what rev of each file it was made to.
Larry, how does BK handle this now? Ive been thinking about this for a
bit and am kind of curious now..
-- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - 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/