From: Petr Baudis <pasky@suse.cz>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Belmar-Letelier <luis@itaapy.com>, git@vger.kernel.org
Subject: Re: cg-mkpatch use case
Date: Wed, 3 May 2006 00:34:38 +0200 [thread overview]
Message-ID: <20060502223438.GH27631@pasky.or.cz> (raw)
In-Reply-To: <46a038f90605021519x5ee680b0v78dd5c092e1b191f@mail.gmail.com>
Dear diary, on Wed, May 03, 2006 at 12:19:00AM CEST, I got a letter
where Martin Langhoff <martin.langhoff@gmail.com> said that...
> On 5/3/06, Petr Baudis <pasky@suse.cz> wrote:
> >not many people actually use it nowadays, I believe. You can apply it
> >back using cg-patch (or even patch itself, or git-apply if you are
> >lucky), but it won't automagically extract the commit message and
> >authorship information.
>
> Erm... I don't personally use it, but cg-patch --long-help tells me...
>
> -c::
> Automatically extract the commit message and authorship information
> (if provided) from the patch and commit it after applying it
> successfuly.
>
> Truth in advertising? ;-)
Uhm, no, it just didn't stick in my mind in the storm of cg-patch
improvements. :-) Oops.
So, YES, there IS a way to apply cg-mkpatches preserving autorship and
everything - cg-patch -c. Sorry for the confusion. ;-)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Right now I am having amnesia and deja-vu at the same time. I think
I have forgotten this before.
prev parent reply other threads:[~2006-05-02 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 7:47 cg-mkpatch use case Belmar-Letelier
2006-05-02 21:41 ` Martin Langhoff
2006-05-02 21:57 ` Petr Baudis
2006-05-02 22:19 ` Martin Langhoff
2006-05-02 22:34 ` Petr Baudis [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=20060502223438.GH27631@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=luis@itaapy.com \
--cc=martin.langhoff@gmail.com \
/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).