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

Re: [RFC] Patches exchange is bad?

From
MCMarco Costalba <mcostalba@yahoo.it>
Date
Aug 17, 2005, 08:27 UTC
Message-ID
<20050817082709.28135.qmail@web26301.mail.ukl.yahoo.com>
Daniel Barkalow wrote:
Show 11 quoted lines
>>2) Practical: The round trip git-format-patch + git-applymbox is the logical and
>>natural way to reach this goal or, also in this case, I intend to stretch some tools,
>>designed for one thing, for something else?
>
>
>I'd guess that git-diff-tree + git-apply (without the rest of the
>scripting) would be more effective when you're not doing anything with the
>intermediate files, since it saves doing a bunch of formatting and
>parsing.
>
>

It would be surely better, but I need to import also the original subject and description. I can use git-diff-tree --pretty -p for the patch creation, but this format is not compatible with git-apply* scripts, and the git command git-apply does not import subject + description info.

Of course I can feed proper subject and description to git-commit but I would like to find something less intrusive as possible, ie. one command for patch export, one command for patch import.

Thanks Marco

__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Next: Martin Langhoff
Message 1 of 2 in “Re: [RFC] Patches exchange is bad?”
  1. Marco CostalbaAug 17, 2005
  2. Martin LanghoffAug 17, 2005

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.