# cg-log gives error on old tags

6 messages from 2005-05-14 to 2005-05-14. Participants: Zack Brown, Petr Baudis.
Thread: https://gitlist.dev/t/621

## Zack Brown, 2005-05-14 15:11

Subject: cg-log gives error on old tags
Message-ID: <20050514151157.GB14184@tumblerings.org>
URL: https://gitlist.dev/e/20050514151157.GB14184%40tumblerings.org

```
I'm seeing the following:

08:10:03 [zbrown] ~/git/cogito$ cg-tag-ls
cogito-0.10     4ed293bc0a5ffca9683e139cad499b69a4c4d569
cogito-0.8      f9f0459b5b39cf83143c91ae39b4eaf187cf678a
cogito-0.9      cc5517b4ea4134c296d4ce2b1d82700c44200c1e
git-pasky-0.1   6bd145ee46a0be6c2ae618379054647121078d8e
git-pasky-0.2   b56ce0c70dbd8d74e63f437555f15aa1462c2075
git-pasky-0.3   2538cadf3e22d768b8eb0d0824ab1e11ac035234
git-pasky-0.4   fba83970090ef54c6eb86dcc2c2d5087af5ac637
git-pasky-0.5   cb18faf513e3903cd57f4c3a5b3547b3ffe3292f
git-pasky-0.6   0605614328f3c150a3dac85904afed5686959335
git-pasky-0.6.1 8a49796121aef48d3030bb1d812cff1491f850fd
git-pasky-0.6.2 55f9d5042603fff4ddfaf4e5f004d2995286d6d3
git-pasky-0.6.3 dd69ca5f806c8b10bb29ecb8d77c88be007c981c
git-pasky-0.7   c83b95297c2a6336c2007548f909769e0862b509
pull_from_pasky 11ed64c1b141c9ba397a1ca76aef2cd250976007
08:10:07 [zbrown] ~/git/cogito$ cg-log -r git-pasky-0.1:git-pasky-0.2
error: cannot map sha1 file 6bd145ee46a0be6c2ae618379054647121078d8e
fatal: git-cat-file 6bd145ee46a0be6c2ae618379054647121078d8e: bad file
Invalid id: 6bd145ee46a0be6c2ae618379054647121078d8e
08:10:14 [zbrown] ~/git/cogito$ 

-- 
Zack Brown

```

## Zack Brown, 2005-05-14 15:19

Subject: Re: cg-log gives error on old tags
Message-ID: <20050514151922.GC14184@tumblerings.org>
URL: https://gitlist.dev/e/20050514151922.GC14184%40tumblerings.org
In-Reply-To: <20050514151157.GB14184@tumblerings.org>

```
I should add, I'm fully current with the cogito origin, with Junio's --author
patch on top.

Z

On Sat, May 14, 2005 at 08:11:57AM -0700, Zack Brown wrote:
> I'm seeing the following:
> 
> 08:10:03 [zbrown] ~/git/cogito$ cg-tag-ls
> cogito-0.10     4ed293bc0a5ffca9683e139cad499b69a4c4d569
> cogito-0.8      f9f0459b5b39cf83143c91ae39b4eaf187cf678a
> cogito-0.9      cc5517b4ea4134c296d4ce2b1d82700c44200c1e
> git-pasky-0.1   6bd145ee46a0be6c2ae618379054647121078d8e
> git-pasky-0.2   b56ce0c70dbd8d74e63f437555f15aa1462c2075
> git-pasky-0.3   2538cadf3e22d768b8eb0d0824ab1e11ac035234
> git-pasky-0.4   fba83970090ef54c6eb86dcc2c2d5087af5ac637
> git-pasky-0.5   cb18faf513e3903cd57f4c3a5b3547b3ffe3292f
> git-pasky-0.6   0605614328f3c150a3dac85904afed5686959335
> git-pasky-0.6.1 8a49796121aef48d3030bb1d812cff1491f850fd
> git-pasky-0.6.2 55f9d5042603fff4ddfaf4e5f004d2995286d6d3
> git-pasky-0.6.3 dd69ca5f806c8b10bb29ecb8d77c88be007c981c
> git-pasky-0.7   c83b95297c2a6336c2007548f909769e0862b509
> pull_from_pasky 11ed64c1b141c9ba397a1ca76aef2cd250976007
> 08:10:07 [zbrown] ~/git/cogito$ cg-log -r git-pasky-0.1:git-pasky-0.2
> error: cannot map sha1 file 6bd145ee46a0be6c2ae618379054647121078d8e
> fatal: git-cat-file 6bd145ee46a0be6c2ae618379054647121078d8e: bad file
> Invalid id: 6bd145ee46a0be6c2ae618379054647121078d8e
> 08:10:14 [zbrown] ~/git/cogito$ 
> 
> -- 
> Zack Brown
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Zack Brown

```

## Petr Baudis, 2005-05-14 15:31

Subject: Re: cg-log gives error on old tags
Message-ID: <20050514153158.GO3905@pasky.ji.cz>
URL: https://gitlist.dev/e/20050514153158.GO3905%40pasky.ji.cz
In-Reply-To: <20050514151922.GC14184@tumblerings.org>

```
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.

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

```

## Zack Brown, 2005-05-14 15:41

Subject: Re: cg-log gives error on old tags
Message-ID: <20050514154121.GD14184@tumblerings.org>
URL: https://gitlist.dev/e/20050514154121.GD14184%40tumblerings.org
In-Reply-To: <20050514153158.GO3905@pasky.ji.cz>

```
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.

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

Only in cogito.broke: cat-file
Only in cogito.broke: check-files
Only in cogito.broke: checkout-cache
Only in cogito.broke: commit-tree
Only in cogito.broke: convert-cache
Only in cogito.broke: diff-cache
Only in cogito.broke: diff-tree
Only in cogito.broke: diff-tree-helper
Only in cogito.broke: fsck-cache
Only in cogito.broke: http-pull
Only in cogito.broke: init-db
Only in cogito.broke: ls-tree
Only in cogito.broke: merge-base
Only in cogito.broke: merge-cache
Only in cogito.broke: read-tree
Only in cogito.broke: rev-list
Only in cogito.broke: rev-tree
Only in cogito.broke: rpull
Only in cogito.broke: rpush
Only in cogito.broke: show-diff
Only in cogito.broke: show-files
Only in cogito.broke: unpack-file
Only in cogito.broke: update-cache
Only in cogito.broke: write-tree

> 
> -- 
> 				Petr "Pasky" Baudis
> Stuff: http://pasky.or.cz/
> C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Zack Brown

```

## Petr Baudis, 2005-05-14 15:51

Subject: Re: cg-log gives error on old tags
Message-ID: <20050514155134.GQ3905@pasky.ji.cz>
URL: https://gitlist.dev/e/20050514155134.GQ3905%40pasky.ji.cz
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

```

## Zack Brown, 2005-05-14 15:53

Subject: Re: cg-log gives error on old tags
Message-ID: <20050514155326.GE14184@tumblerings.org>
URL: https://gitlist.dev/e/20050514155326.GE14184%40tumblerings.org
In-Reply-To: <20050514155134.GQ3905@pasky.ji.cz>

```
On Sat, May 14, 2005 at 05:51:34PM +0200, Petr Baudis wrote:
> 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?

Nothing really.

> 
> > 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.

That's what I figured. But I thought one of the cg-updates would have been
a cg-rm to get rid of them.

Z

> 
> -- 
> 			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
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Zack Brown

```
