From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Nanako Shiraishi <nanako3@lavabit.com>,
Johannes Sixt <j.sixt@viscovery.net>,
John Tapsell <johnflux@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: Confusing git pull error message
Date: Fri, 09 Oct 2009 17:57:04 -0700 [thread overview]
Message-ID: <7vbpkgf4m7.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 7vy6nl10fg.fsf@alter.siamese.dyndns.org
Junio C Hamano <gitster@pobox.com> writes:
> Nanako Shiraishi <nanako3@lavabit.com> writes:
>
>> Quoting Jeff King <peff@peff.net>
>>
>>> Subject: [PATCH] pull: improve advice for unconfigured error case
>>> ...
>> Junio, may I ask what happened to this patch?
>
> Thanks for prodding. Unfortunately I lost track. Will look at it again
> but probably not tonight.
Applied the patch as-is, as it looked quite good.
Thanks.
next prev parent reply other threads:[~2009-10-10 1:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 20:01 Confusing git pull error message John Tapsell
2009-09-12 21:11 ` Jeff King
2009-09-12 21:31 ` John Tapsell
2009-09-12 22:34 ` Jeff King
2009-09-12 21:37 ` Sverre Rabbelier
2009-09-12 22:31 ` Jeff King
2009-09-12 22:37 ` Sverre Rabbelier
2009-09-13 20:38 ` Junio C Hamano
2009-09-13 20:42 ` Jeff King
2009-09-13 20:57 ` Junio C Hamano
2009-09-13 21:36 ` Jeff King
2009-09-13 22:11 ` Junio C Hamano
2009-09-13 20:57 ` John Tapsell
2009-09-13 21:18 ` Junio C Hamano
2009-09-13 21:16 ` Junio C Hamano
2009-09-13 22:39 ` Jeff King
2009-09-14 11:14 ` Jeff King
2009-10-05 11:32 ` Johannes Sixt
2009-10-05 11:53 ` Jeff King
2009-10-05 12:13 ` Johannes Sixt
2009-10-05 19:08 ` Junio C Hamano
2009-10-05 19:12 ` Jeff King
2009-10-05 19:35 ` Jeff King
2009-10-08 22:01 ` Nanako Shiraishi
2009-10-09 7:38 ` Junio C Hamano
2009-10-10 0:57 ` Junio C Hamano [this message]
2009-10-05 19:36 ` Junio C Hamano
2009-10-05 22:00 ` Jeff King
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=7vbpkgf4m7.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=johnflux@gmail.com \
--cc=nanako3@lavabit.com \
--cc=peff@peff.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).