git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Errors pushing tags in "next"

From
Junio C Hamano <junkio@cox.net>
Date
Mar 23, 2007, 09:17 UTC
Message-ID
<7vps70qpx8.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20070323090213.GA7186@fiberbit.xs4all.nl>
Marco Roeland <marco.roeland@xs4all.nl> writes:
Show 16 quoted lines
>> Luben Tuikov <ltuikov@yahoo.com> writes:
>> 
>> > BTW, git has always said to me "Pushing version ... to the masses"
>> > whenever I'd do "git-push --tags web".
>> 
>> Sorry, I must be blind, and git-grep is too.
>> 
>> $ git grep -e 'to the masses' -e 'Pushing v'
>> 
>> returns absolutely empty.
>
> The line comes from an older version of templates/hooks--update. The
> line was removed in commit 829a686f1b50ba96cac2d88494fa339efe0c0862 .
>
> So Luben does seem to have a hook installed, perhaps this is the
> culprit.

Thanks for spotting this. I do not use this hook (well, I only use commit-msg, pre-commit, and pre-rebase patches) and it was totally outside of my radar.

It runs describe to find the previous tag, but the parser is a bit old fashioned. It says:

	prev=$(git describe "$3^" | sed 's/-g.*//')
but modern way to say the same is:
	prev=$(git describe --abbrev=0 "$3^")
Luben, sorry for the trouble.

I do not know how much better the recent hooks--update is compared to the version you use. It is supposed to be backward compatible, so you _might_ want to simply update it with the one from 'master' after checking if it suits your needs. Otherwise, I think the above one-liner should work the problem around.

Previous: Marco RoelandNext: Luben Tuikov
Message 8 of 12 in “Errors pushing tags in "next"”
  1. Luben TuikovMar 23, 2007
  2. Junio C HamanoMar 23, 2007
  3. Luben TuikovMar 23, 2007
  4. Junio C HamanoMar 23, 2007
  5. Luben TuikovMar 23, 2007
  6. Junio C HamanoMar 23, 2007
  7. Marco RoelandMar 23, 2007
  8. Junio C HamanoMar 23, 2007
  9. Luben TuikovMar 23, 2007
  10. Luben TuikovMar 23, 2007
  11. Andy ParkinsMar 23, 2007
  12. Luben TuikovMar 23, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.