Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Add $$(PKG)_AUTORECONF_ENV argument to autotools package
Date: Thu, 17 Jul 2014 20:43:50 +0200	[thread overview]
Message-ID: <20140717204350.6cedbf85@free-electrons.com> (raw)
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801148D7154@tss-server1.home.tropicalstormsoftware.com>

Dear Rick Taylor,

On Thu, 17 Jul 2014 12:21:54 +0000, Rick Taylor wrote:

> I haven't aggressively tested it against buildroot master I'm afraid
> as we have a load of extra infrastructure around buildroot so we
> stick to full releases, and we are just evaluating 2014.05.
> 
> I shall update the docs/manual/adding-packages-autotools.txt and
> resubmit the patches.

Thanks for the explanation. However, we have received this e-mail with
a "PATCH 1/1" title even though it doesn't contain a patch, and then
the documentation update as PATCH 2/2.

In a nutshell, assuming you have a branch named "autoreconf-env" with
two patches on top of the "master" branch, what you should do to send
your patches is:

	git format-patch master

Then review the 0001-<foo>.patch and 0002-<bar>.patch to make sure
everything is in order. And then:

	git send-email --to buildroot at uclibc.org *.patch

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-07-17 18:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 12:21 [Buildroot] [PATCH 1/1] Add $$(PKG)_AUTORECONF_ENV argument to autotools package Rick Taylor
2014-07-17 18:43 ` Thomas Petazzoni [this message]
2014-07-18  8:21   ` Rick Taylor
2014-07-18  8:29     ` Thomas Petazzoni
2014-07-18  8:53       ` Thomas De Schampheleire
  -- strict thread matches above, loose matches on Subject: below --
2014-07-17  9:36 Rick Taylor
2014-07-17  9:44 ` Thomas Petazzoni

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=20140717204350.6cedbf85@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox