From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Validate nicknames of remote branches to prohibit confusing ones
Date: Sat, 16 Feb 2008 00:08:37 -0800 [thread overview]
Message-ID: <7v1w7dcohm.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0802152209560.13593@iabervon.org> (Daniel Barkalow's message of "Fri, 15 Feb 2008 22:11:38 -0500 (EST)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> On Fri, 15 Feb 2008, Junio C Hamano wrote:
>
>> Daniel Barkalow <barkalow@iabervon.org> writes:
>> ...
>> > I was sort of expecting you to just put this in yourself, but since you
>> > haven't, I wrote it up as an actual patch and fixed the polarity of the
>> > test for slashes.
>>
>> Thanks. I am bogged down in day-job these days and have been
>> down-sick for the past 36 hours.
>
> No problem. It's an easy enough patch, and the test suite found the bug in
> the original version. I just wanted to make sure it didn't get forgotten
> on account of never getting a patch emailled to the list.
Actually I have been slowly trying to give up on being in the
business of tying up loose ends left by everybody. I used to
touch-up and finish obvious loose ends and add tests myself to
patches from many people, and I still try to do so when able,
but as contributor base gets larger, doing so to all incoming
patches is starting to become unfeasible, and it is not quite
fair to me (and my wife ;-)).
So in that sense, yes it was getting forgotten, waiting for a
"this is the final revision, apply it" message from you.
prev parent reply other threads:[~2008-02-16 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 19:14 [PATCH] Validate nicknames of remote branches to prohibit confusing ones Daniel Barkalow
2008-02-15 22:22 ` Junio C Hamano
2008-02-16 3:11 ` Daniel Barkalow
2008-02-16 8:08 ` Junio C Hamano [this message]
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=7v1w7dcohm.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.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).