Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ehmanns <universeii@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Added OK/FAIL output to SNMP init script.
Date: Thu, 25 Feb 2016 22:05:24 +0100	[thread overview]
Message-ID: <56CF6C94.4050301@gmx.de> (raw)
In-Reply-To: <20160225220417.7df2cbca@free-electrons.com>

Thomas,
thanks for the clarification.

Regards,
Andreas

Am 25.02.2016 um 22:04 schrieb Thomas Petazzoni:
> Hello,
>
> On Thu, 25 Feb 2016 21:43:48 +0100, Andreas Ehmanns wrote:
>
>> one "stupid" questions. Shall the patches be incremental or relative to
>> the original file?
>> Example: Change some lines and create the first patch. Then change the
>> next things based on the original file or based on the already patched file?
> Based on the already patched file of course, otherwise you won't go
> very far. You need to create a patch series. To do this, create a Git
> branch, make a set of commits that stack on top of each other, and then
> use git format-patch to create one patch file for each commit in your
> branch, and send them with git send-mail.
>
> You can look in the Buildroot manual, there are some explanations about
> this:
>
>     http://nightly.buildroot.org/#submitting-patches
>
> Best regards,
>
> Thomas

      reply	other threads:[~2016-02-25 21:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 17:31 [Buildroot] [PATCH 1/1] Added OK/FAIL output to SNMP init script Andreas Ehmanns
2016-02-25  9:46 ` Thomas Petazzoni
2016-02-25 20:02   ` Andreas Ehmanns
2016-02-25 20:25     ` Thomas Petazzoni
2016-02-25 20:43       ` Andreas Ehmanns
2016-02-25 21:04         ` Thomas Petazzoni
2016-02-25 21:05           ` Andreas Ehmanns [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=56CF6C94.4050301@gmx.de \
    --to=universeii@gmx.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