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

Re: git-push and $GIT_DIR/branches

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 7, 2008, 22:27 UTC
Message-ID
<7vfxm3f9z8.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20081107204451.GA10394@auto.tuwien.ac.at>
mkoegler@auto.tuwien.ac.at (Martin Koegler) writes:
> I asume, that you [and probably many other] are not very interrested
> in this feature. But would you accept a patch changing the push
> refspec to HEAD:refs/heads/<head>?

I believe "git-push foo" with .git/branches/foo has worked the way it does now from day one, so the above change you suggest breaks peoples' expectations and documented behaviour, _if_ people are using "branches" with git-push. It definitely is a no-go to just change the behaviour without warning and deprecation period, but with a careful transition plan, I personally do not think there is a fundamental reason not to improve it (others may disagree).

I do not know what Cogito did when you told it to push with such a configuration, though. Its "branches" had quite different semantics from the concept of "remote" in git.

Previous: Martin Koegler
Message 3 of 3 in “git-push and $GIT_DIR/branches”
  1. Martin KoeglerNov 7, 2008
  2. Martin KoeglerNov 7, 2008
  3. Junio C HamanoNov 7, 2008

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.