[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug-patch] Re: GNU patch: new 2.6 release
From: |
Björn Gustavsson |
Subject: |
[bug-patch] Re: GNU patch: new 2.6 release |
Date: |
Sat, 14 Nov 2009 13:27:38 +0100 |
2009/11/14 Andreas Gruenbacher <address@hidden>:
> 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
[bug-patch] Re: GNU patch: new 2.6 release, Björn Gustavsson, 2009/11/15