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

Re: git clone operation

From
MGMike Gant <mwgant@gmail.com>
Date
Aug 20, 2008, 02:27 UTC
Message-ID
<8f282e3b0808191927t7c202a2dvdff678bcec60d87f@mail.gmail.com>
In-Reply-To
<8f282e3b0808191923w18001cc6sef828d94b35e40c6@mail.gmail.com>
Show 17 quoted lines
> Thanks for your responses. I appreciate you guys taking the time to answer.
>
> After thinking about this, I still don't understand when I clone a
> repo why I will
> get the equivalent of whatever branch is active at the time of cloning? What
> was the process that led to this design decision?
>
> So that also got me thinking about work flows with git. Because of the way clone
> works it seems that you wouldn't want someone to clone your every day "work"
> repository? So do developers generally have a separate repository that they push
> to and others can clone? This repository may have only a 'master' branch (but
> probably others I seem to recall Junio describing other branches in the main git
> repository). Is this a 'normal' work flow?
>
> Thanks,
> Mike Gant
>

Also, I meant to add if the above work flow is the git way of development, is this the purpose of a bare repository?

Previous: Mike Gant
Message 5 of 5 in “git clone operation”
  1. Mike GantAug 17, 2008
  2. Jakub NarebskiAug 17, 2008
  3. Björn SteinbrinkAug 17, 2008
  4. Mike GantAug 20, 2008
  5. Mike GantAug 20, 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.