From: Michael J Gruber <git@drmicha•warpmail.net>
To: Junio C Hamano <gitster@pobox•com>
Cc: git@vger•kernel.org, Pete Harlan <pgit@pcharlan•com>,
Jeff King <peff@peff•net>
Subject: Re: [PATCH] clone: report check out for non-bare clones
Date: Wed, 12 May 2010 09:59:33 +0200 [thread overview]
Message-ID: <4BEA5FE5.3060503@drmicha.warpmail.net> (raw)
In-Reply-To: <7vljbp994c.fsf@alter.siamese.dyndns.org>
Junio C Hamano venit, vidit, dixit 12.05.2010 03:55:
> Michael J Gruber <git@drmicha•warpmail.net> writes:
>
>> In the case of a detached head, (null) is the branch name.
>
> I think that depends on your particular libc implementation that helpfully
> makes printf("%s", NULL) not to at least dump core.
Sorry, I didn't know I can't rely on that. I'll change that if going
this route (reporting check out) is desirable at all. Is it?
Michael
next prev parent reply other threads:[~2010-05-12 7:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-09 1:23 [PATCH/RFC] clone: have progress report mention top level dir, not git dir Pete Harlan
2010-05-09 11:02 ` Jeff King
2010-05-09 20:09 ` [PATCH v2 0/2] clone: simplify progress message Pete Harlan
2010-05-09 20:10 ` [PATCH v2 1/2] clone: have progress report mention top level dir, not git dir Pete Harlan
2010-05-09 20:11 ` [PATCH v2 2/2] clone: add bare clone to the progress message Pete Harlan
2010-05-09 22:15 ` [PATCH v2 0/2] clone: simplify " Junio C Hamano
2010-05-09 23:10 ` Pete Harlan
2010-05-10 5:47 ` Jeff King
2010-05-10 10:31 ` Michael J Gruber
2010-05-10 14:46 ` [PATCH] clone: report check out for non-bare clones Michael J Gruber
2010-05-12 1:55 ` Junio C Hamano
2010-05-12 7:59 ` Michael J Gruber [this message]
2010-05-10 23:22 ` [PATCH v2 0/2] clone: simplify progress message Pete Harlan
2010-05-11 7:27 ` Michael J Gruber
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=4BEA5FE5.3060503@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=pgit@pcharlan$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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