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] fix broken path in arm_toolchain_defconfig
Date: Fri, 21 May 2010 09:48:15 +0200	[thread overview]
Message-ID: <20100521094815.2513c09a@surf> (raw)
In-Reply-To: <AANLkTinRRSrYrySzAmiv7zEqUAW_L60IY7bgRH2ZQlHP@mail.gmail.com>

On Fri, 21 May 2010 15:12:13 +0800
Chih-Min Chao <cmchao@gmail.com> wrote:

> So, should I generate the patch by "git format-patch --signoff
> revision_range" ??

It is usually at commit time that the signed-off line is added, by
doing :

  git commit -s

instead of just

  git commit

Typical very basic work-flow :

 # Assuming you are on master

 # Create a new branch for your work and switch to this branch
 git checkout -b mywork

 # Hack hack hack

 # Commit your work (supposing you want to all changes in a single
 # commit, which may or may not be appropriate)
 git commit -a -s

 # Format the patch (or patches)
 git format-patch master

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

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-05-21  7:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14  8:12 [Buildroot] [PATCH] fix broken path in arm_toolchain_defconfig Chih-Min Chao
2010-05-19 11:34 ` Thomas Petazzoni
2010-05-21  7:12   ` Chih-Min Chao
2010-05-21  7:48     ` Thomas Petazzoni [this message]
2010-05-22 20:08     ` Peter Korsgaard

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=20100521094815.2513c09a@surf \
    --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