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

Re: git clone -b

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 2, 2013, 18:21 UTC
Message-ID
<7vppv0960p.fsf@alter.siamese.dyndns.org>
In-Reply-To
<51D274AA.2050902@atlas-elektronik.com>
Stefan Näwe <stefan.naewe@atlas-elektronik.com> writes:
Show 7 quoted lines
>> While I wasn't paying much attention to this, I vaguely recall that
>> people pointed out that using a fresh clone every time may not be
>> what you want to do in the first place, and I happen to agree with
>> them (and that is why I am not very much interested in this topic).
>  
> As I said: We'd be using 'git archive --remote...' if that was
> submodule-aware.

That would still have to transfer full material enough to populate the working tree for a single revision. I was wondering why "clone once, and then update incrementally with 'fetch && reset --hard' && clean'" is not used, if the tree is for a build-bot.

Previous: Stefan NäweNext: Phil Hord
Message 8 of 10 in “git clone -b”
  1. Stefan NäweJun 28, 2013
  2. Stefan NäweJun 28, 2013
  3. Fredrik GustafssonJun 28, 2013
  4. Stefan NäweJun 28, 2013
  5. Stefan NäweJul 1, 2013
  6. Junio C HamanoJul 1, 2013
  7. Stefan NäweJul 2, 2013
  8. Junio C HamanoJul 2, 2013
  9. Phil HordJul 1, 2013
  10. Jeff KingJul 3, 2013

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.