From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Jerry Van Baren <gvb.linuxppc.dev@gmail.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: Stupid git question: adding acked-by
Date: Sat, 08 Dec 2007 22:04:59 -0800 [thread overview]
Message-ID: <475B858B.9010900@am.sony.com> (raw)
In-Reply-To: <475B7B41.4000505@gmail.com>
On 12/08/2007 09:21 PM, Jerry Van Baren wrote:
> OK git gurus, this is something I have not figured out: the best way to
> add acked-by (or additional signed-off-by) lines to git patches.
>
> What I'm talking about is when I've applied a patch to my repo and
> published the change on the list and get an "acked-by" back. By the
> time I get the ack, the acked patch may be several patches deep. My
> current technique is to reset the repo, edit the patch(es) to add the
> "acked-by" lines, and then re-apply the patches. PITA and probably the
> stupidest way.
>
> Stacked git should work (effectively does the same thing but more
> gracefully), but I have not gone that route yet.
>
> There must be a better way, if only I could find the right (of 137)
> git-* command...
I keep patches in a repo. I just update the patch header and commit.
-Geoff
next prev parent reply other threads:[~2007-12-09 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 5:21 Stupid git question: adding acked-by Jerry Van Baren
2007-12-09 6:04 ` Geoff Levand [this message]
2007-12-09 6:22 ` Grant Likely
2007-12-09 6:43 ` Stephen Rothwell
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=475B858B.9010900@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=gvb.linuxppc.dev@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).