git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] rev-parse --symbolic-full-name: don't print '^' if SHA1 is not a ref
Date: Fri, 23 May 2008 17:02:00 -0700	[thread overview]
Message-ID: <7v3ao8r2mf.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 4836D0F1.4090007@viscovery.net

Johannes Sixt <j.sixt@viscovery.net> writes:

> From: Johannes Sixt <johannes.sixt@telecom.at>
>
> The intention of --symbolic-full-name is to not print anything if a
> revision is not an exact ref. But this command:
>
>     $ git-rev-parse --symbolic-full-name --not master~1
>
> still emitted a sole '^' to stdout (provided that there's no other ref at
> master~1).

Well spotted.  Thanks.

      reply	other threads:[~2008-05-24  0:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 14:13 [PATCH] rev-parse --symbolic-full-name: don't print '^' if SHA1 is not a ref Johannes Sixt
2008-05-24  0:02 ` 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=7v3ao8r2mf.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.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).