if you think it's normal the thing sounds very messy. I mean, how can
a changeset be numbered 1.879.43.1 and not be included in 2.5.59?
The way I understood it is that when Linus merges "stuff", this "stuff"
gets a changeset number in the future, not in the past. No matter if the
"stuff" was created in the past. Is this the case or not?
I mean, somehow there must be a way to number the changesets so that
applying them in order generates something coherent.
Andrea
-
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/