Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] manual: update review process and patchwork
Date: Mon, 14 Oct 2013 23:22:46 +0200	[thread overview]
Message-ID: <87li1vmtsp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1381351575-16776-1-git-send-email-rjbarnet@rockwellcollins.com> (Ryan Barnett's message of "Wed, 9 Oct 2013 15:46:15 -0500")

>>>>> "Ryan" == Ryan Barnett <rjbarnet@rockwellcollins.com> writes:

 Ryan> Adding more documentaiton based on discussion from the mailing list
 Ryan> in regards the buildroot review process and how patchworks can be
 Ryan> used to pull in patches for testing purposes.

 Ryan> Mailing list discussion:
 Ryan> http://lists.busybox.net/pipermail/buildroot/2013-September/078170.html

 Ryan> Signed-off-by: Ryan Barnett <rjbarnet@rockwellcollins.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2013-10-14 21:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 20:46 [Buildroot] [PATCH v4 1/1] manual: update review process and patchwork Ryan Barnett
2013-10-10 10:10 ` Thomas De Schampheleire
2013-10-14 21:22 ` 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=87li1vmtsp.fsf@dell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox