From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: "Gary V. Vaughan" <git@mlists.thewrittenword.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/5] Not all vendor diffs support GNUisms (resend)
Date: Sun, 25 Apr 2010 18:20:26 +0200 [thread overview]
Message-ID: <4BD46BCA.3010308@lsrfire.ath.cx> (raw)
In-Reply-To: <20100425152130.GA27695@thor.il.thewrittenword.com>
Am 25.04.2010 18:03, schrieb Gary V. Vaughan:
> Apologies for the long delay before my resent repost... it took me
> until now to figure out why most of my messages to this lest were
> being rejected...
>
> On Sun, Apr 25, 2010 at 04:57:56PM +0200, Ren? Scharfe wrote:
>> Am 25.04.2010 10:35, schrieb Gary V. Vaughan:
>>>> (I'd split the introduction of DIFF/$DIFF, the diff -> test_cmp
>>>> conversions and the change to set GIT_TEST_CMP=cmp for your platform
>>>> into three separate patches.)
>>>
>>> Will do. And then I'll resubmit the whole series.
>>
>> Commits c296134d and 4a2284b9 from Junio (in git 1.7.1) already do some
>> part of the work, converting two test script to test_cmp.
>
> Excellent. ETA on a release from that branch so that I can finish any
> necessary changes to my outstanding changesets?
>
> ...or is there time for me to clone the repository and rebase those
> changes in time for the 1.7.1 release?
Junio released git 1.7.1 just yesterday.
René
next prev parent reply other threads:[~2010-04-25 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 16:30 [PATCH 2/5] Not all vendor diffs support GNUisms (resend) Gary V. Vaughan
2010-03-11 19:23 ` René Scharfe
2010-04-25 8:35 ` Gary V. Vaughan
2010-04-25 14:57 ` René Scharfe
2010-04-25 16:02 ` Gary V. Vaughan
2010-04-25 16:20 ` René Scharfe [this message]
2010-04-26 16:50 ` Gary V. Vaughan
2010-04-26 19:00 ` René Scharfe
2010-06-12 16:24 ` Scott Chacon
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=4BD46BCA.3010308@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@mlists.thewrittenword.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).