From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Jim Meyering <jim@meyering.net>, gdb@sourceware.org, hjl.tools@gmail.com
Subject: Re: sourceware.org gitweb gives some wrong results
Date: Sat, 24 Mar 2012 14:40:00 -0000 [thread overview]
Message-ID: <20120324144004.GA21014@host2.jankratochvil.net> (raw)
In-Reply-To: <m2mx76p7e5.fsf@linux-m68k.org>
On Sat, 24 Mar 2012 12:26:10 +0100, Andreas Schwab wrote:
> Jim Meyering <jim@meyering.net> writes:
>
> > Part of the problem is that the reference, "master", is ambiguous:
>
> No, it isn't. master can never refer to refs/heads/cvs/master. See
> git-rev-parse(1) for the precise rules for refname lookup.
It is a gitweb bug. I have verified it on latest gitweb and filed:
https://code.google.com/p/git-core/issues/detail?id=10
Till it gets fixed the workaround would be simple.
Regards,
Jan
prev parent reply other threads:[~2012-03-24 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120322171255.GA23769@host2.jankratochvil.net>
2012-03-24 10:49 ` Jim Meyering
2012-03-24 11:26 ` Andreas Schwab
2012-03-24 14:40 ` Jan Kratochvil [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=20120324144004.GA21014@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jim@meyering.net \
--cc=schwab@linux-m68k.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 read-only IMAP folder(s) and NNTP newsgroup(s).