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

Re: Multiple checkouts of the same repository

From
MMMatt McCutchen <hashproduct+git@gmail.com>
Date
Oct 1, 2006, 21:04 UTC
Message-ID
<3bbc18d20610011404x52d8ba15ib51ac2a7060bd25e@mail.gmail.com>
In-Reply-To
<Pine.LNX.4.63.0610012116310.14200@wbgn013.biozentrum.uni-wuerzburg.de>
On 10/1/06, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> The fact is, your setup is fragile, and I think that is hard to fix if you
> do not make A and B git repositories in their own right.

I think my setup is much simpler than having two separate repositories that update each other using hooks. What can go wrong, besides the scenario I mentioned where one working tree doesn't get updated when I commit through the other one?

Matt
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 5 of 8 in “Multiple checkouts of the same repository”
  1. Matt McCutchenOct 1, 2006
  2. Johannes SchindelinOct 1, 2006
  3. Matt McCutchenOct 1, 2006
  4. Johannes SchindelinOct 1, 2006
  5. Matt McCutchenOct 1, 2006
  6. Johannes SchindelinOct 2, 2006
  7. Daniel BarkalowOct 3, 2006
  8. Junio C HamanoOct 3, 2006

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.