From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Apologies
Date: Thu, 2 Aug 2012 22:13:19 +0200 [thread overview]
Message-ID: <20120802221319.380170fc@skate> (raw)
Hello,
As you have probably seen, you have received hundreds of commit
e-mails. These are due to the fact that I rebased and pushed the next
branch to start accumulating non bug fix changes that will be
integrated into the 2012.11 release.
However, I apparently didn't do that the way Peter was doing it, and
the commit e-mail scripts decided to send one e-mail for each of the
new commits that appeared in the next branch since the last time it was
rebased. So basically, you're going to see *all* the commits that
happened during the 2012.08 cycle :-(
I guess that I should have deleted the next branch completely, and then
push a completely new branch. The end result would have been the same,
except for the hundreds of e-mails.
My sincere apologies for the mess.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2012-08-02 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 20:13 Thomas Petazzoni [this message]
2012-08-02 22:27 ` [Buildroot] Apologies Grant Edwards
2012-08-26 9:13 ` Peter Korsgaard
2012-08-26 9:18 ` Thomas Petazzoni
2012-08-26 9:12 ` Peter Korsgaard
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=20120802221319.380170fc@skate \
--to=thomas.petazzoni@free-electrons.com \
--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.