From: "Christian MICHON" <christian.michon@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "git list" <git@vger.kernel.org>
Subject: Re: patches in context format ?
Date: Mon, 12 Jan 2009 10:57:42 +0100 [thread overview]
Message-ID: <46d6db660901120157g49aa8f8eo957cf4a0f5d279f0@mail.gmail.com> (raw)
In-Reply-To: <20090112095250.GB3079@coredump.intra.peff.net>
On Mon, Jan 12, 2009 at 10:52 AM, Jeff King <peff@peff.net> wrote:
> 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 !
prev parent reply other threads:[~2009-01-12 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 9:00 patches in context format ? Christian MICHON
2009-01-12 9:28 ` Junio C Hamano
2009-01-12 9:52 ` Christian MICHON
2009-01-12 9:34 ` Teemu Likonen
2009-01-12 9:53 ` Christian MICHON
2009-01-12 9:52 ` Jeff King
2009-01-12 9:57 ` Christian MICHON [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=46d6db660901120157g49aa8f8eo957cf4a0f5d279f0@mail.gmail.com \
--to=christian.michon@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).