From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Apologies
Date: Sun, 26 Aug 2012 11:12:06 +0200 [thread overview]
Message-ID: <87sjbaow49.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20120802221319.380170fc@skate> (Thomas Petazzoni's message of "Thu, 2 Aug 2012 22:13:19 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Hello,
Thomas> As you have probably seen, you have received hundreds of commit
Thomas> e-mails. These are due to the fact that I rebased and pushed the next
Thomas> branch to start accumulating non bug fix changes that will be
Thomas> integrated into the 2012.11 release.
Thomas> However, I apparently didn't do that the way Peter was doing it, and
Thomas> the commit e-mail scripts decided to send one e-mail for each of the
Thomas> new commits that appeared in the next branch since the last time it was
Thomas> rebased. So basically, you're going to see *all* the commits that
Thomas> happened during the 2012.08 cycle :-(
Thomas> I guess that I should have deleted the next branch completely, and then
Thomas> push a completely new branch. The end result would have been the same,
Thomas> except for the hundreds of e-mails.
Yes, I normally delete the branch and create a new one as the 2 branches
have nothing in common (except for the name).
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-08-26 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 20:13 [Buildroot] Apologies Thomas Petazzoni
2012-08-02 22:27 ` Grant Edwards
2012-08-26 9:13 ` Peter Korsgaard
2012-08-26 9:18 ` Thomas Petazzoni
2012-08-26 9:12 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sjbaow49.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.