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

RE: Git-new-workdir

From
CCCraig L. Ching <cching@mqsoftware.com>
Date
May 21, 2008, 19:30 UTC
Message-ID
<63BEA5E623E09F4D92233FB12A9F794301FC8B2B@emailmn.mqsoftware.com>
In-Reply-To
<MnNeABMJjOQ8gdG6gY5zubSC3c5X2sDYBwcI1MotmXFvW3kUNXzB5A@cipher.nrlssc.navy.mil>
Show 7 quoted lines
> From: Brandon Casey [mailto:casey@nrlssc.navy.mil] 
> My take on it...
> 
> If you want to have _multiple_different_ branches checked out 
> from the _same_ repository, and do development in all of 
> them, then git-new-workdir is the right choice.
>

Yes, that's precisely what we want to do. So according to your experience, we're making the right choice then.

Show 5 quoted lines
> If you want to have the _same_branch_ checked out in multiple 
> work directories, then cloning with -s is what you want. In 
> this case I assume development will be performed in the 
> original repo, and the clones will do a pull to update.
> 
Ok, for us this would probably be rare, but good to know.
Show 5 quoted lines
> Personally, I have found the git-new-workdir script to 
> satisfy any need which caused me to even think about cloning 
> with -s. I am hoping the functionality of git-new-workdir 
> will be folded into git porcelain at some point (ahem J Schindelin).
> 
We'd like that too ;-)
> -brandon
> 
>

Cheers, Craig

Previous: Brandon CaseyNext: Brandon Casey
Message 5 of 7 in “Git-new-workdir”
  1. Craig L. ChingMay 21, 2008
  2. Luciano RochaMay 21, 2008
  3. Craig L. ChingMay 21, 2008
  4. Brandon CaseyMay 21, 2008
  5. Craig L. ChingMay 21, 2008
  6. Brandon CaseyMay 21, 2008
  7. Craig L. ChingMay 21, 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.