Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Documentation update : add tips to build manual, add information about buildroot toolchain not being relocable and put some hints to use it, move the Beyond Buildroot section before FAQs and add content
Date: Wed, 06 Feb 2013 09:32:00 +0100	[thread overview]
Message-ID: <51121500.6000602@relinux.de> (raw)
In-Reply-To: <CAKvQZ_15jd18pfvWaWKKa5XMkNNXe41G2YTSJ-QX=dcmQBRrTA@mail.gmail.com>

Am 05.02.2013 21:53, schrieb Willy Lambert:
> 2013/2/5 Samuel Martin <s.martin49@gmail.com>:
>> Hi Willy,
>>
>> 2013/2/5 Willy Lambert <lambert.willy@gmail.com>:
>>> 2013/1/25 Willy Lambert <lambert.willy@gmail.com>:
>> [...]
>>>> No no, ack on all this. I'll resend a corrected patch. What's the
>>>> process ? should I do something particular or just sending a patch
>>>> again is fine ?
>> Well, almost nothing more than what is explained here:
>> http://buildroot.org/downloads/manual/manual.html#submitting-patches
>>
>> When running 'git format-patch' you should add:
>> --subject-prefix="PATCH v2"
>> to make clear it's a new version of a previous patchset.
>>
>> [...]
>>> I did the correction and (hard) try to send the mail to the mailing
>>> list with send mail. I think it's not yet perfect, sry :(
> Send failed first time, I retry with different configuration, it should work.
I failed with this some time ago, too. According to Peter's hint I now
always use git send-email --annotate and edit manually.

You should leave one blank line after the header in the commit message.

Regards

Stephan
>
>> Regards,
>>
>> --
>> Samuel
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

      reply	other threads:[~2013-02-06  8:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 13:16 [Buildroot] [PATCH 1/1] Documentation update : add tips to build manual, add information about buildroot toolchain not being relocable and put some hints to use it, move the Beyond Buildroot section before FAQs and add content Willy Lambert
2013-01-23 20:27 ` Samuel Martin
2013-01-23 20:29   ` Samuel Martin
2013-01-24 20:19 ` Samuel Martin
2013-01-25 11:14   ` Willy Lambert
2013-02-05 16:15     ` Willy Lambert
2013-02-05 16:40       ` Samuel Martin
2013-02-05 20:53         ` Willy Lambert
2013-02-06  8:32           ` Stephan Hoffmann [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=51121500.6000602@relinux.de \
    --to=sho@relinux.de \
    --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