git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Christian MICHON" <christian.michon@gmail.com>
To: "git list" <git@vger.kernel.org>
Subject: patches in context format ?
Date: Mon, 12 Jan 2009 10:00:11 +0100	[thread overview]
Message-ID: <46d6db660901120100g7f62a0c2k68c96cbfc23dab5@mail.gmail.com> (raw)

I'm maintaining a git tree of the vim project: this work can be seen
at http://github.com/cmichon/vim

vim patches do not come as unified format, but only as context format
instead (from a "diff -c").

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 ?

I guess the answer is no, but has anyone on the list been working on
this ? is there another way to translate from "context" to "unified"
format ?

TIA

-- 
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !

             reply	other threads:[~2009-01-12  9:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12  9:00 Christian MICHON [this message]
2009-01-12  9:28 ` patches in context format ? 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

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=46d6db660901120100g7f62a0c2k68c96cbfc23dab5@mail.gmail.com \
    --to=christian.michon@gmail.com \
    --cc=git@vger.kernel.org \
    /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).