[Buildroot] Apologies

[Buildroot] Apologies

[Thomas Petazzoni]

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

[Buildroot] Apologies

[Grant Edwards]

On 2012-08-02, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> 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.

Another reason to read the list via gmane.org's NNTP server. My slrn
scorefile defaults to hiding commit messages.  :)

-- 
Grant Edwards               grant.b.edwards        Yow! Are you the
                                  at               self-frying president?
                              gmail.com            

[Buildroot] Apologies

[Peter Korsgaard]

>>>>> "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

[Buildroot] Apologies

[Peter Korsgaard]

>>>>> "Grant" == Grant Edwards <grant.b.edwards@gmail.com> writes:

 Grant> On 2012-08-02, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
 >> 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.

 Grant> Another reason to read the list via gmane.org's NNTP server. My slrn
 Grant> scorefile defaults to hiding commit messages.  :)

We could move the git commit mails to a seperate commit list if a lot of
people don't want to see them.

-- 
Bye, Peter Korsgaard

[Buildroot] Apologies

[Thomas Petazzoni]

Le Sun, 26 Aug 2012 11:13:06 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :

>  Grant> Another reason to read the list via gmane.org's NNTP server. My slrn
>  Grant> scorefile defaults to hiding commit messages.  :)
> 
> We could move the git commit mails to a seperate commit list if a lot of
> people don't want to see them.

Unless there is a strong wish to move into this direction, I'd prefer
to keep the commit messages on the main mailing list. It lets people
know what has been changed, it encourages review of the committed
changes, etc.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com