Git development
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: Zack Brown <zbrown@tumblerings.org>
Cc: git@vger.kernel.org
Subject: Re: cg-log gives error on old tags
Date: Sat, 14 May 2005 17:51:34 +0200	[thread overview]
Message-ID: <20050514155134.GQ3905@pasky.ji.cz> (raw)
In-Reply-To: <20050514154121.GD14184@tumblerings.org>

Dear diary, on Sat, May 14, 2005 at 05:41:21PM CEST, I got a letter
where Zack Brown <zbrown@tumblerings.org> told me that...
> On Sat, May 14, 2005 at 05:31:58PM +0200, Petr Baudis wrote:
> > Dear diary, on Sat, May 14, 2005 at 05:19:22PM CEST, I got a letter
> > where Zack Brown <zbrown@tumblerings.org> told me that...
> > > I should add, I'm fully current with the cogito origin, with Junio's --author
> > > patch on top.
> > 
> > Hmm, works here. I forgot to update the tags immediately after the big
> > rehashing, so you could get them from that time and rsync wouldn't
> > overwrite them. Try deleting them from .git/refs/tags/ and re-pull.
> 
> Well, I did a fresh clone of cogito, and the problem went away. Weird.

Yes, so you did an equivalent of removing the old tags and re-pulling.
What's weird on it?

> But now I notice that some files from the broken tree are not in the new tree:

Those are old git executables from before the big renaming to use git-
prefix for those. Harmless.

-- 
			Petr "Pasky the avid GIT Traffic reader" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor

  reply	other threads:[~2005-05-14 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-14 15:11 cg-log gives error on old tags Zack Brown
2005-05-14 15:19 ` Zack Brown
2005-05-14 15:31   ` Petr Baudis
2005-05-14 15:41     ` Zack Brown
2005-05-14 15:51       ` Petr Baudis [this message]
2005-05-14 15:53         ` Zack Brown

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=20050514155134.GQ3905@pasky.ji.cz \
    --to=pasky@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=zbrown@tumblerings.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