From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Rework cvsexportcommit to handle binary files for all cases.
Date: Tue, 14 Nov 2006 07:49:04 +0100 [thread overview]
Message-ID: <200611140749.05023.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <7vveli4zxc.fsf@assigned-by-dhcp.cox.net>
tisdag 14 november 2006 01:47 skrev Junio C Hamano:
>Robin Rosenberg wrote:
>> I sent a patch earlier, which was not applied, due to imperfections that I
>> cannot solve fully. One issue was that patch 2.5.9 was required and hacking
>> it to handle binary diffs with spaces would require and even worse kludge,
>
>I suspect that we should not be using patch, but instead be
>using git-apply perhaps with -C option if people want fuzz.
Does git-apply work without a git repo? We're applying patches onto a CVS
repo.
>[...]
> I know this script originally came from southern hemisphere, but
> I was talking about _western_ hemisphere. The comment refers to
> the part of the code the attached patch fixes, which I will
> apply along with your updated patch.
Western/nothern, both apply to where I live.
>[...]
>I think scripts that work with git
> plumbing should read from -z output when they need to and are
> capable of, as we have done for git-cvsserver recently, and
> things written in Perl certainly are capable of doing so.
I'll investgate that.
next prev parent reply other threads:[~2006-11-14 6:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-12 15:29 [PATCH] Rework cvsexportcommit to handle binary files for all cases Robin Rosenberg
2006-11-13 4:39 ` Junio C Hamano
2006-11-13 20:39 ` Robin Rosenberg
2006-11-14 0:47 ` Junio C Hamano
2006-11-14 6:49 ` Robin Rosenberg [this message]
2006-11-14 6:56 ` Junio C Hamano
2006-11-13 20:40 ` Robin Rosenberg
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=200611140749.05023.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).