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

Re: prevent push of irrelevant tags

From
RLRolf Leggewie <foss@rolf.leggewie.biz>
Date
Apr 12, 2012, 20:45 UTC
Message-ID
<4F873EE2.5090203@rolf.leggewie.biz>
In-Reply-To
<7v1uns67f4.fsf@alter.siamese.dyndns.org>
Hamano-San,
thank you very much for the ultra-quick reply and your explanation.
On 13.04.2012 04:07, Junio C Hamano wrote:
Show 8 quoted lines
>> Git has the information to know...
> 
> No, it doesn't.  
> 
>>  that tag X will be useless in repo Y
>> because the commit Z it points to does not exist in Y.
> 
> Think of a case where:
I am only a simple user so I hope you will not be angry with me if I
misunderstand you.  I believe you are saying that "git push" does not
have the necessary information which I take your word for.  But git
itself surely should know if commit Z is available from repo Y or am I
mistaken?  For example I can do "git log repoY:master|grep $ZcommitID".
 That would return empty if the master branch at repoY didn't have
information about Z*.
Thank you for bearing with me.
Regards
Rolf
* Of course, it's possible that Z is not part of master but another
  branch at Y.
Previous: Junio C HamanoNext: Andreas Schwab
Message 3 of 4 in “prevent push of irrelevant tags”
  1. Rolf LeggewieApr 12, 2012
  2. Junio C HamanoApr 12, 2012
  3. Rolf LeggewieApr 12, 2012
  4. Andreas SchwabApr 12, 2012

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.