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

Re: git remote set-head not working?

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 18, 2009, 21:42 UTC
Message-ID
<7veimst0w6.fsf@alter.siamese.dyndns.org>
In-Reply-To
<76718490912181328k5f87d82u499b7a1eba471126@mail.gmail.com>
Jay Soffian <jaysoffian@gmail.com> writes:
Show 7 quoted lines
> On Fri, Dec 18, 2009 at 12:38 PM, Eugene Sajine <euguess@gmail.com> wrote:
>> Yes. I was trying to change the HEAD on the bare remote (origin) repo
>> and the concept here is really confusing.
>
> The remote command is about updating things under .git/refs/remotes,
> not about updating a remote server. For updating a remote server,
> there is really only push. Clear as mud?

We still support (and unfortunately we would probably end up supporting for a long time) "remote update" so it is not strictly true, but that is the original motivation behind "git remote" subcommand.

> Understood. I'm not sure whether the send-pack/receive-pack protocol
> supports the notion of "I want to change what HEAD points to."

It does not support it, but that is not because there is a strong reason it shouldn't.

Previous: Jay SoffianNext: Jay Soffian
Message 5 of 7 in “git remote set-head not working?”
  1. Eugene SajineDec 18, 2009
  2. Jeff KingDec 18, 2009
  3. Eugene SajineDec 18, 2009
  4. Jay SoffianDec 18, 2009
  5. Junio C HamanoDec 18, 2009
  6. Jay SoffianDec 18, 2009
  7. Eugene SajineDec 18, 2009

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.