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

Re: git push tags

From
DNDrew Northup <n1xim.email@gmail.com>
Date
Oct 25, 2012, 21:16 UTC
Message-ID
<CAM9Z-nkosbe1NXYnu7x6v4seLqCnMBWg-jrdH2eJ9RetaZBTyQ@mail.gmail.com>
In-Reply-To
<CAB9Jk9A95YrrtH8ue-CJ6Mqe9Z+3nfo=tjurLZjmecfiMFijvg@mail.gmail.com>

On Thu, Oct 25, 2012 at 3:05 PM, Angelo Borsotti <angelo.borsotti@gmail.com> wrote: ---At 13:19 on Oct 25, 2012, Drew Northup wrote: [added for clarity]

Show 8 quoted lines
>>Tags have many uses. Some of those uses are harmed when tags change
> and some aren't. That's a philosophical argument
>
> I agree, but in this case the computer does not provide any means to
> implement the same strategy on tags as it does instead on local
> repositories. Why I must force a change on a tag in the local
> repository and instead I can change it without any forcing in a remote
> one?

Changing the tag in the local repository is a tag modification operation. Pushing that change to a remote repository DOES NOT execute "git tag...." in the remote. Plain and simple the two are different operations.

> Are remote repositories less protected than the local ones? I
> think that to be consistent, the same strategy should be used on all
> repositories, i.e. rejecting changes on tags by default, unless they
> are forced.

So here we come to the core argument. Is sounds to me like you want changes to remote tags to work differently from push updates to ALL other references. The required change, if I'm not mistaken, would be for tags to not permit fast-forward updates while all other references would be pushed normally. From my brief and un-enlightened look at the push code I can't see that being as easy as it sounds.

In any case, I think your complaint stems from thinking that "git tag" is the operation being performed on the remote when in fact it is not. Given the mayhem that changing this may involve I'm not going to claim it to be a good idea.

-- 
-Drew Northup
--------------------------------------------------------------
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59
Previous: Angelo BorsottiNext: Angelo Borsotti
Message 4 of 35 in “git push tags”
  1. Angelo BorsottiOct 25, 2012
  2. Drew NorthupOct 25, 2012
  3. Angelo BorsottiOct 25, 2012
  4. Drew NorthupOct 25, 2012
  5. Angelo BorsottiOct 26, 2012
  6. Drew NorthupOct 26, 2012
  7. Chris RorvickOct 26, 2012
  8. Drew NorthupOct 26, 2012
  9. Chris RorvickOct 26, 2012
  10. Angelo BorsottiOct 26, 2012
  11. Kacper KornetOct 26, 2012
  12. Drew NorthupOct 26, 2012
  13. Kacper KornetOct 26, 2012
  14. Angelo BorsottiOct 26, 2012
  15. Kacper KornetOct 26, 2012
  16. Drew NorthupOct 26, 2012
  17. Johannes SixtOct 28, 2012
  18. Chris RorvickOct 28, 2012
  19. Philip OakleyOct 28, 2012
  20. Drew NorthupOct 28, 2012
  21. Chris RorvickOct 29, 2012
  22. Angelo BorsottiOct 29, 2012
  23. Angelo BorsottiOct 29, 2012
  24. Michael HaggertyOct 29, 2012
  25. Jeff KingOct 29, 2012
  26. Drew NorthupOct 29, 2012
  27. Angelo BorsottiOct 29, 2012
  28. Jeff KingOct 29, 2012
  29. Drew NorthupOct 29, 2012
  30. Angelo BorsottiOct 29, 2012
  31. Kacper KornetOct 29, 2012
  32. Jeff KingOct 29, 2012
  33. Chris RorvickOct 30, 2012
  34. Kacper KornetOct 29, 2012
  35. Chris RorvickOct 30, 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.