Re: Changelogs on kernel.org

[David Woodhouse]

[e-mail] said:
> It's probably best if you simply view this as a BK limitation which
> isn't going away any time soon and don't put junk changesets in the
> middle of your stream of changes.  It's easy enough to export the
> change you want as a patch, export the comments in the form that bk
> comments wants, undo the junk changeset, import the patch, and set the
> comments.  Yeah, it's awkward; consider that a feedback loop which
> encourages you to think a bit more about what you put in the tree.

What it actually encourages is for people to have multiple throwaway trees. 
(Which isn't quite so much of a BK turnoff once you discover compilercache.)

If the tree's going to be thrown away anyway, it doesn't matter if it gets 
confused -- how about making it a little easier to backport changesets -- 
surely it should be possible to make BK import a changeset iff all the 
affected files are identical in both trees before the changeset? 

--
dwmw2