From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
"J. Bakshi" <joydeep@infoservices.in>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: can I use multiple worktree in same git repo ?
Date: Thu, 21 Jul 2011 20:22:15 +0200 [thread overview]
Message-ID: <20110721182215.GA9505@kolya> (raw)
In-Reply-To: <m3sjpzsdll.fsf@localhost.localdomain>
On Thu, Jul 21, 2011 at 11:17:57AM -0700, Jakub Narebski wrote:
> Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:
>
> > On Wed, Jul 20, 2011 at 7:54 PM, J. Bakshi <joydeep@infoservices.in> wrote:
> > > As a result whenever there is a commit , it updates the related folder in filesystem.
> > > Say a commit at svn->mysite-repo->dir1->trunk->src ==> modify ==> /var/www/demo/dir1
> > >
> > > Can I do the same in git with multiple worktree ? possible ?
> >
> > Using multiple worktree with the same repo won't work in git because
> > the repo also have worktree-related information. [...]
> [...]
> > Also have a look at git-new-workdir in contrib directory of git
> > repository. I don't use it but you might find it useful.
>
> Actually with git-new-workdir you can have multiple working
> directories associated with single repository, by the way of symlinks.
>
> Note however that if you intend to *work* in those workdirs, they
> better correspond to different branches... or you can mess something
> heavy.
It would be possible to use the .git-file feature here. Then symlinks are
avoided and the solution is portable.
Med vänliga hälsningar
Fredrik
next prev parent reply other threads:[~2011-07-21 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 12:54 can I use multiple worktree in same git repo ? J. Bakshi
2011-07-20 13:25 ` Nguyen Thai Ngoc Duy
2011-07-20 16:12 ` J. Bakshi
2011-07-21 3:20 ` Nguyen Thai Ngoc Duy
2011-07-21 6:07 ` J. Bakshi
2011-07-21 18:17 ` Jakub Narebski
2011-07-21 18:22 ` Fredrik Gustafsson [this message]
2011-07-21 18:50 ` Jakub Narebski
2011-07-22 9:06 ` Sergio
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=20110721182215.GA9505@kolya \
--to=iveqy@iveqy.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=joydeep@infoservices.in \
--cc=pclouds@gmail.com \
/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).