From: Sergei Organov <osv@javad.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Bug in git-show-branch, or in core-tutorial?
Date: Thu, 01 Nov 2007 15:11:42 +0300 [thread overview]
Message-ID: <87zlxy2mip.fsf@osv.gnss.ru> (raw)
In-Reply-To: <7v8x5ictrx.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Thu\, 01 Nov 2007 00\:24\:50 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> I think that is a simple typo of "these", not "three".
No, the explanation text explicitly mentions merge~1 revision that is
not there in the git-show-branch output, so those "three" is consistent
with explanation text itself, but not with git-show-branch output.
--
Sergei.
prev parent reply other threads:[~2007-11-01 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 20:17 Bug in git-show-branch, or in core-tutorial? Sergei Organov
2007-11-01 7:24 ` Junio C Hamano
2007-11-01 12:11 ` Sergei Organov [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=87zlxy2mip.fsf@osv.gnss.ru \
--to=osv@javad.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.