From: "Matt McCutchen" <hashproduct+git@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Multiple checkouts of the same repository
Date: Sun, 1 Oct 2006 17:04:36 -0400 [thread overview]
Message-ID: <3bbc18d20610011404x52d8ba15ib51ac2a7060bd25e@mail.gmail.com> (raw)
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
next prev parent reply other threads:[~2006-10-01 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 19:03 Multiple checkouts of the same repository Matt McCutchen
2006-10-01 19:08 ` Johannes Schindelin
2006-10-01 19:14 ` Matt McCutchen
2006-10-01 19:17 ` Johannes Schindelin
2006-10-01 21:04 ` Matt McCutchen [this message]
2006-10-02 10:16 ` Johannes Schindelin
2006-10-03 2:52 ` Daniel Barkalow
2006-10-03 7:59 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3bbc18d20610011404x52d8ba15ib51ac2a7060bd25e@mail.gmail.com \
--to=hashproduct+git@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).