Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org, hjl.tools@gmail.com
Subject: Re: sourceware.org gitweb gives some wrong results
Date: Sat, 24 Mar 2012 10:49:00 -0000	[thread overview]
Message-ID: <871uoixoj7.fsf@rho.meyering.net> (raw)
In-Reply-To: <20120322171255.GA23769@host2.jankratochvil.net> (Jan	Kratochvil's message of "Thu, 22 Mar 2012 18:12:55 +0100")

Jan Kratochvil wrote:
> Hi Jim,
>
> http://sourceware.org/git/?p=gdb.git;a=summary
> -> head master
> http://sourceware.org/git/?p=gdb.git;a=tree;h=refs/heads/master;hb=master
> -> gdb/
> http://sourceware.org/git/?p=gdb.git;a=tree;f=gdb;h=b2bc1d8ff2d63dad7f98166d07ea4851a8e33b9e;hb=master
> -> NEWS blob
> http://sourceware.org/git/?p=gdb.git;a=blob;f=gdb/NEWS;h=696de32204d3cb449595343c41c073266ab79747;hb=master
>  = OK, "*** Changes since GDB 7.4"
> -> NEWS raw
> http://sourceware.org/git/?p=gdb.git;a=blob_plain;f=gdb/NEWS;hb=master
>  = wrong, "*** Changes since GDB 6.8"
>    ^^^^^
>    !!!!!
>
> in my copy it works fine:
> http://git.jankratochvil.net/?p=gdb.git;a=blob_plain;f=gdb/NEWS;hb=master
>  = OK, "*** Changes since GDB 7.4"
>
> I wanted to give a reference to mail and I had to use my gitweb for it.

Hi Jan,

[Cc'ing the list, in the unlikely event that anyone is using cvs/master:
 it has not been modified since Dec 2008]

Part of the problem is that the reference, "master", is ambiguous:

    sourceware$ git show-ref master
    22ff147254a15c977ca7eccc83567ba74587b8a3 refs/heads/cvs/master
    4959fdc11a310d335e57a69f597b64e1c155cefa refs/heads/hjl/x32/master
    f4a023ee8a2015d98fd3aeb50a5ccde2f201ec46 refs/heads/master

What you're getting is the first one: refs/heads/cvs/master:

    $ git show refs/heads/cvs/master:gdb/NEWS |sed 4q|tail -1
    *** Changes since GDB 6.8

What you want is the last one:

    $ git show refs/heads/master:gdb/NEWS |sed 4q|tail -1
    *** Changes since GDB 7.4

One way to fix this is to rename cvs/master and hjl/x32/master
so that there is no longer any ambiguity.

It's not impossible that this would be fixed by upgrading sourceware.org's
gitweb (currently at 1.7.3.4, it seems; while the latest is 1.7.9)
You can manually specify the full ref spec, too, but
you shouldn't have to resort to that:

  http://sourceware.org/git/?p=gdb.git;a=blob_plain;f=gdb/NEWS;hb=refs/heads/master

If you want to go for the rename, HJ can rename his branch
however he sees fit, but I'd have to rename the cvs/master one,
since it's also in the cvs-to-git source mirror, while HJ's branch
is present only in the public destination mirror.  I'll have to
rename cvs/master both in the private source, and in the public dest.

I propose to do both renames, like this:

    git branch -m cvs/master cvs/old-master
    git branch -m hjl/x32/master hjl/x32-master


       reply	other threads:[~2012-03-24 10:49 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 [this message]
2012-03-24 11:26   ` Andreas Schwab
2012-03-24 14:40     ` Jan Kratochvil

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=871uoixoj7.fsf@rho.meyering.net \
    --to=jim@meyering.net \
    --cc=gdb@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=jan.kratochvil@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox