Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] DEVELOPERS: add myself to packages
Date: Tue, 07 Nov 2017 17:27:50 +0100	[thread overview]
Message-ID: <8760amuk8p.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20171107145434.0d5c0b6b@windsurf> (Thomas Petazzoni's message of "Tue, 7 Nov 2017 14:54:34 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > Hello,
 > On Tue, 07 Nov 2017 13:03:20 +0100, Peter Korsgaard wrote:
 >> >>>>> "Matt" == Matt Weber <matthew.weber@rockwellcollins.com> writes:  
 >> 
 >> > Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>  
 >> 
 >> Committed to next, thanks (it could have gone to master, but to limit
 >> merge conflicts I guess next is better).

 > Merging to next is a bit sad, as it means that none of the autobuilder
 > failures that will occur on those packages will be reported to Matthew,
 > until next is merged back in master. Indeed, I use the "master" branch
 > to decide to whom which autobuilder failure should be sent to.

 > So I would have preferred to see this patch in master. Yes, it will
 > conflict with changes to the DEVELOPERS file merged in next for new
 > package additions, but those conflicts are trivial to resolve.

True - I've cherry picked this on master as well, so we have the best of
both worlds.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2017-11-07 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07  1:08 [Buildroot] [PATCH] DEVELOPERS: add myself to packages Matt Weber
2017-11-07 12:03 ` Peter Korsgaard
2017-11-07 13:54   ` Thomas Petazzoni
2017-11-07 14:05     ` Matthew Weber
2017-11-07 16:27     ` 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=8760amuk8p.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox