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

Re: [RFC] Patches exchange is bad?

From
Junio C Hamano <junkio@cox.net>
Date
Aug 16, 2005, 21:02 UTC
Message-ID
<7vzmrh8uis.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20050816200132.88287.qmail@web26304.mail.ukl.yahoo.com>
Marco Costalba <mcostalba@yahoo.it> writes:
> It is just a very thin layer above the two git scripts, the only extra work 
> is the cleaning up of some info that git-format-patch-script automatically adds, 
> so that the new commits look like the originals (i.e. same header and description).
> What do you think?

All good. The existing tools are designed to work well in the following workflow:

    $ git format-patch --mbox master..pu
    $ cat 000[234]-*.txt >to-apply
    $ git checkout master
    $ git applymbox to-apply
    $ mv .git/refs/heads/pu .git/refs/heads/old-pu
    $ git checkout -b pu master
    $ git applymbox 0001-*.txt

to advance "master" with selected commits, possibly reordered, from the "pu" branch, and rebase the "pu" branch using the remaining commits.

I would like to know a bit about "git format-patch" adding extra info that you needed to get rid of. It shouldn't be necessary.

Previous: Johannes SchindelinNext: Martin Langhoff
Message 3 of 5 in “[RFC] Patches exchange is bad?”
  1. Marco CostalbaAug 16, 2005
  2. Johannes SchindelinAug 16, 2005
  3. Junio C HamanoAug 16, 2005
  4. Martin LanghoffAug 16, 2005
  5. Catalin MarinasAug 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.