From: "Grant Likely" <grant.likely@secretlab.ca>
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, 8 Dec 2007 23:22:03 -0700 [thread overview]
Message-ID: <fa686aa40712082222o2001bc23y377d82e213b111a0@mail.gmail.com> (raw)
In-Reply-To: <475B7B41.4000505@gmail.com>
On 12/8/07, Jerry Van Baren <gvb.linuxppc.dev@gmail.com> wrote:
> Stacked git should work (effectively does the same thing but more
> gracefully), but I have not gone that route yet.
This is my preferred solution, but you don't have to do it this way.
>
> There must be a better way, if only I could find the right (of 137)
> git-* command...
Try git-cherry-pick. Get a list of the SHA-1 patch ids and reset your
branch. Then cherry pick each patch with the -e flag. Git will pull
up an editor and let you edit the commit message before applying so
you can add the Acked-by line.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-12-09 6:22 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
2007-12-09 6:22 ` Grant Likely [this message]
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=fa686aa40712082222o2001bc23y377d82e213b111a0@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--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).