From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Generating patches against packages source code
Date: Sat, 29 Dec 2012 18:13:01 +0100 [thread overview]
Message-ID: <20121229181301.37d3d131@skate> (raw)
In-Reply-To: <20121229170948.GA15925@mail.sceen.net>
Dear Richard Braun,
On Sat, 29 Dec 2012 18:09:48 +0100, Richard Braun wrote:
> On Sat, Dec 29, 2012 at 06:54:01PM +0200, Stefan Fr?berg wrote:
> > Ah, I was hoping (because Im lazy ;-) ) that I don't need to add
> > manually all those
> > Signed-off lines.
>
> You don't.
>
> > I was always wondering how other people add all those several inside
> > Signed-off lines when submitting one big patch to this list.
>
> See git help format-patch. This command has an option -s (--signoff)
> to automatically produce the signed-off lines.
Please read the discussion before saying things that are out of topic.
Stefan is *NOT* talking about adding Signed-off-by lines to Buildroot
patches, but Signed-off-by lines to patches against packages in
Buildroot, i.e the patches that go in
package/<pkg>/<pkg>-something.patch.
And those patches are not necessarily generated with Git. They can be
manually generated with diff, generated with quilt, etc.
So, no, the story is not as simple as adding the -s option to git
commit or git format-patch, because Stefan is maybe not using git to
generate patches for the packages.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-12-29 17:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 1:45 [Buildroot] (no subject) Stefan Fröberg
2012-12-29 1:45 ` [Buildroot] [PATCH 1/5] mesa3d: bumped to 8.0.5 Stefan Fröberg
2012-12-29 8:06 ` Thomas Petazzoni
2012-12-29 13:06 ` Stefan Fröberg
2012-12-29 1:45 ` [Buildroot] [PATCH 2/5] " Stefan Fröberg
2012-12-29 8:07 ` Thomas Petazzoni
2012-12-29 1:45 ` [Buildroot] [PATCH 3/5] " Stefan Fröberg
2012-12-29 8:08 ` Thomas Petazzoni
2012-12-29 1:45 ` [Buildroot] [PATCH 4/5] " Stefan Fröberg
2012-12-29 1:45 ` [Buildroot] [PATCH 5/5] " Stefan Fröberg
2012-12-29 8:08 ` Thomas Petazzoni
2012-12-29 7:59 ` [Buildroot] (no subject) Thomas Petazzoni
2012-12-29 14:13 ` Stefan Fröberg
2012-12-29 14:32 ` Thomas Petazzoni
2012-12-29 14:56 ` Stefan Fröberg
2012-12-29 15:23 ` [Buildroot] (no subject) git format-patch Carsten Schoenert
2012-12-29 15:31 ` Stefan Fröberg
2012-12-29 16:15 ` [Buildroot] Generating patches against packages source code Thomas Petazzoni
2012-12-29 16:54 ` Stefan Fröberg
2012-12-29 17:09 ` Richard Braun
2012-12-29 17:13 ` Thomas Petazzoni [this message]
2012-12-29 17:33 ` Richard Braun
2012-12-29 18:03 ` Yann E. MORIN
2012-12-29 18:39 ` Thomas Petazzoni
2012-12-29 19:04 ` Stefan Fröberg
2012-12-29 19:56 ` Yann E. MORIN
2012-12-29 20:18 ` Stefan Fröberg
2012-12-29 19:52 ` Yann E. MORIN
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=20121229181301.37d3d131@skate \
--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