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

Re: patches in context format ?

From
Christian MICHON <christian.michon@gmail.com>
Date
Jan 12, 2009, 09:57 UTC
Message-ID
<46d6db660901120157g49aa8f8eo957cf4a0f5d279f0@mail.gmail.com>
In-Reply-To
<20090112095250.GB3079@coredump.intra.peff.net>
On Mon, Jan 12, 2009 at 10:52 AM, Jeff King <peff@peff.net> wrote:
Show 32 quoted lines
> On Mon, Jan 12, 2009 at 10:00:11AM +0100, Christian MICHON wrote:
>
>> The current solution I have is to use the original patch command,
>> stage modifications and add new files. I do not like this solution,
>> because I have to work out the commit messages out of the mbox and I
>> lose reproducibility. I'm basically maintaining a subset of shell
>> scripts, the original patches and an artificial way (ugly) to get
>> timestamps of modifications (for the commit dates).
>>
>> Instead of this complicated procedure, I'd like to use "git apply" or
>> "git am", provided I can get git to support "context output format" as
>> input for patches ?
>
> Maybe this is not the nicest solution if you are going to apply a lot of
> these patches, but you can pick up where git-am fails, run patch, and
> ask it to resume:
>
>  $ git am mbox-with-context-diff
>  Applying: a minor change
>  error: No changes
>  Patch failed at 0001.
>  When you have resolved this problem run "git am --resolved".
>  If you would prefer to skip this patch, instead run "git am --skip".
>  To restore the original branch and stop patching run "git am --abort".
>
>  $ patch <.git/rebase-apply/patch ;# or whatever
>  $ git add -u
>  $ git am -r
>  Applying: a minor change
>
> -Peff
>

vim patches are in hundredth... so I guess this is too manual. Thanks for the suggestion!

-- 
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !
Previous: Jeff King
Message 7 of 7 in “patches in context format ?”
  1. Christian MICHONJan 12, 2009
  2. Junio C HamanoJan 12, 2009
  3. Christian MICHONJan 12, 2009
  4. Teemu LikonenJan 12, 2009
  5. Christian MICHONJan 12, 2009
  6. Jeff KingJan 12, 2009
  7. Christian MICHONJan 12, 2009

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.