On Mon, Oct 19, 2015 at 1:13 PM, hasufell <hasuf...@gentoo.org> wrote: > > We already know that. But if e.g. ago runs his scripts at 00:00 with > ~300 packages stabilized, the history (without git command line) on > github/gitweb will be fun to read (and people DO that). >
It doesn't seem like it would have been any better in the cvs days, but I guess that isn't a reason to reject this on its own. If this was about changing the copyright headers in all the ebuilds in the tree I'd say that this is a million related trivial changes that can be merged. Nobody needs to see that in the history broken out. However, stabilizing a single package really is an impactful change. The fact that you're doing 100 of them at one time doesn't really diminish the impact of each one. Any of them could break a system or need to be reverted. If they're being done at once because they're all part of some library stabilization then I'd combine them into a commit, because they are actually related. Maybe what is needed is better tools for tagging/filtering history? -- Rich
