From: Junio C Hamano <gitster@pobox.com>
To: markus.heidelberg@web.de
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH resend] bash completion: add 'rename' subcommand to git-remote
Date: Wed, 21 Jan 2009 02:26:32 -0800 [thread overview]
Message-ID: <7veiyxeyzr.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 200901201921.10223.markus.heidelberg@web.de
Markus Heidelberg <markus.heidelberg@web.de> writes:
> Junio C Hamano, 17.01.2009:
>> "Shawn O. Pearce" <spearce@spearce.org> writes:
>>
>> > Markus Heidelberg <markus.heidelberg@web.de> wrote:
>> >>
>> >> Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>
>> >
>> > Acked-by: Shawn O. Pearce <spearce@spearce.org>
>> >
>> >> I've just accidently read in the completion file itself, that
>> >> Shawn is the maintainer, so I give it a third try. The first two
>> >> haven't been sent to him.
>> >
>> > Sorry, I must have missed the other two attempts. :-)
>>
>> And I seem to have missed all three.
>
> I really don't like to bother you again, but compared to the inclusion
> of the other patches, I guess you have forgotten the third try of this
> patch.
>
> Thus this fourth try :)
I did not mean that I forgot by the above "I seem to have missed".
Literally none of your three attempts seem to have reached me. I can
guess what you wrote from the _included_ text in Shawn's response, but
that is not a good/right place for me to pick up a patch from, is it?
next prev parent reply other threads:[~2009-01-21 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200901162254.58300.markus.heidelberg@web.de>
2009-01-16 22:12 ` [PATCH resend] bash completion: add 'rename' subcommand to git-remote Shawn O. Pearce
2009-01-17 8:03 ` Junio C Hamano
2009-01-20 18:21 ` Markus Heidelberg
2009-01-21 10:26 ` Junio C Hamano [this message]
2009-01-21 22:59 ` Markus Heidelberg
2009-01-08 18:53 [PATCH, " Markus Heidelberg
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=7veiyxeyzr.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=markus.heidelberg@web.de \
--cc=spearce@spearce.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).