On Mon, 2005-04-18 at 02:35 +0200, Petr Baudis wrote: > > For the special case of removing history before 2.6.12-rc2 from the > > trees, I certainly think we can do it by leaving out all the commits, > > not just the trees. We can do that easily, but there's no way we can > > _add_ that history retrospectively if we omit it in the first place. > > I'm confused by this paragraph, but that might be my English skills > failing somehow.
"For the general case of people pruning their own trees, _maybe_ you're right that it would be good to keep the commits even if we delete the actual trees. But for history older than 2.6.12-rc2, that's a special case -- I think we can happily delete the commits too. "We can delete old trees/commits easily, but we can't _add_ them to the existing linux-2.6.git tree, because the oldest commit in that tree (b4ceb6e27e4cc3f37d26e04c4535c79b98a9f889) doesn't have a parent." -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
