----- Original Message ----- > Hi team, > > There could be another way if we can't drop old-style ChangeLog for > some reason: > do not alter ChangeLog (i.e. use commit log instead) until the patch > is fully accepted (e.g., Andrew could get log notes (one or even > several) from git log of processed patches (of master > savannah/master) and update ChangeLog (as a separate commit). > No magic, just deferred update. >
No. Updating the ChangeLog is a requirement. > Regards, > Ivan > > Mon, 15 Oct 2012 09:31:59 +0300 от Pekka Enberg <penb...@kernel.org>: > > > > > > > On Sun, Oct 14, 2012 at 11:55 PM, Andrew Hughes < > gnu.and...@redhat.com > wrote: > >> May be it's time to change the policy of patch acceptance from > >> "please find a person who reviews (among 1 or 2 guys) your code" > >> to > >> "if signed FSF paper, and you have patches, post them to ML, > >> commit > >> to some feature development branch and, if no objections within > >> 2-3 > >> weeks, merge the branch to master, in case of further objections > >> revert the patches". > > > > No, I don't think this is suitable. > > And more importantly, not really necessary now that we're using Git. > That said, we really need to do something with ChangeLog because it > causes unnecessary rejects when merging from one git tree to another. > Can we drop it or did someone have some Git magic to deal with it? > > Pekka > > -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: 248BDC07 (https://keys.indymedia.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07
