It's listed on the wiki that explains how to maintain branches :)
On Sun, Aug 17, 2008 at 2:32 PM, John Freeman <[EMAIL PROTECTED]> wrote: > Christopher Faylor wrote: >> >> On Sat, Aug 16, 2008 at 02:35:08PM +0200, Manuel L?pez-Ib??ez wrote: >> >>> >>> Dear GCC devs, >>> >>> Please do *not* use the full logs of the merged revisions as the >>> commit message of a merge. Apart from making the output of svn log >>> useless, commits messages are parsed are tracked for PR numbers, the >>> commit message is added to the bugzilla page of the PR and people >>> subscribed to the relevant PR in bugzilla are notified of the commit. >>> Therefore a single merge of many revisions would result in a flood of >>> mails sent for no good reason and they make a mess of the bugzilla >>> page. >>> >>> I am sure many of you have been hit by this recently. Please, let's >>> try to avoid this. >>> >> >> If that isn't a good enough reason, doing this completely swamps >> gcc.gnu.org as it valiantly attempts to send all of the above email. >> This resulted in a load average of 24 on the system last night and kept >> me awake until 2:30AM trying to stabilize things. >> >> cgf >> > > I'm just going to come out and admit that it was probably me who caused all > this. I appreciate the anonymity afforded by everyone, and I apologize. I > promise I will not make this mistake again. In my defense, I want to say > that your reasons are good enough, but I did not know them beforehand. No > one informed me of any commit policies when I was given subversion access. > I thought that since I was working on a branch, I had free reign. > Education would go a long way in preventing future errors. > > - John >
