From: "Björn Gustavsson" <bgustavsson@gmail.com>
To: bug-patch@gnu.org
Cc: git@vger.kernel.org
Subject: Re: GNU patch: new 2.6 release
Date: Sat, 14 Nov 2009 13:27:38 +0100 [thread overview]
Message-ID: <6672d0160911140427p549dfe66p454376eaed346704@mail.gmail.com> (raw)
In-Reply-To: <200911141117.29238.agruen@suse.de>
2009/11/14 Andreas Gruenbacher <agruen@suse.de>:
> Support for git's extended header lines for renames, copies, hashes, file
> modes would be great. I'll happily take patches or eventually implement it
> myself. Binary patches are not as high on my wish list, but feel free to send
> code.
Support for the other extended header lines would be useful for me too.
I might have a go at implementing them (and binary patches) at some
point in the future.
>> That would be very useful in a workflow when you work in git (and have some
>> binary files in the repository), but need to commit your finished work
>> into another VCS (such as Clearcase).
>
> Isn't there a better way to do this than with patches?
If there is a better way, I would be very interested in finding out what it is.
Feeding the output from 'git format-patch' to patch is the
best way I've had come up with yet. patch (given the '-g 1' option)
will automatically check out the files that are to be patched.
I have wrapped that in a simple script that retrieves the commit
comment from the patch and check in the files with that commit
comment.
/Björn
--
Björn Gustavsson, Erlang/OTP, Ericsson AB
next prev parent reply other threads:[~2009-11-14 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 0:09 GNU patch: new 2.6 release Andreas Gruenbacher
2009-11-14 8:45 ` Björn Gustavsson
2009-11-14 10:17 ` Andreas Gruenbacher
2009-11-14 12:27 ` Björn Gustavsson [this message]
2009-11-15 13:37 ` Thomas Rast
2009-11-15 14:02 ` Björn Gustavsson
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=6672d0160911140427p549dfe66p454376eaed346704@mail.gmail.com \
--to=bgustavsson@gmail.com \
--cc=bug-patch@gnu.org \
--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).