git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: cg-mkpatch use case

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
May 2, 2006, 22:19 UTC
Message-ID
<46a038f90605021519x5ee680b0v78dd5c092e1b191f@mail.gmail.com>
In-Reply-To
<20060502215703.GK27689@pasky.or.cz>
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? ;-)
cheers,
martin
Previous: Petr BaudisNext: Petr Baudis
Message 4 of 5 in “cg-mkpatch use case”
  1. Belmar-LetelierMay 2, 2006
  2. Martin LanghoffMay 2, 2006
  3. Petr BaudisMay 2, 2006
  4. Martin LanghoffMay 2, 2006
  5. Petr BaudisMay 2, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.