From: Joshua Jensen <jjensen@workspacewhiz.com>
To: Julian Phillips <julian@quantumfyre.co.uk>
Cc: Gustavo Narea <gnarea@tech.2degreesnetwork.com>, git@vger.kernel.org
Subject: Re: Multiple checkouts active for the same repository
Date: Fri, 24 Sep 2010 10:32:50 -0600 [thread overview]
Message-ID: <4C9CD2B2.3030106@workspacewhiz.com> (raw)
In-Reply-To: <14b089955184bbb677b6434993682403@212.159.54.234>
----- Original Message -----
From: Julian Phillips
Date: 9/24/2010 9:33 AM
> The git-new-workdir script to be found in contrib/workdir allows multiple
> working copies to share the same repository - though there are some
> caveats:
>
> 1) uses symbolic links, so doesn't work on Windows
Windows Vista and Windows 7 both support proper file and directory
symbolic links. According to my experimentation the other day with
git-new-workdir on Windows 7:
* Windows - mklink /D creates a directory symbolic link. mklink creates
a file symbolic link. The file system traverses into the symbolic link
and back out of it just like Unix. rmdir /S deletes just the directory
symbolic link. Windows Explorer's delete does the same.
* Cygwin - 'ln -s' does not create a true directory symbolic link.
Cygwin seems to understand the symbolic link, but Windows itself
doesn't. 'rm -f' properly deletes a directory symbolic link.
* Bash included with msysGit - 'ln -s' performs a file/directory copy.
'rm -f' whacks the directory contents of the linked directory and then
deletes the symbolic link. Ick. :(
Josh
next prev parent reply other threads:[~2010-09-24 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 9:29 Multiple checkouts active for the same repository Gustavo Narea
2010-09-24 11:55 ` Gustavo Narea
2010-09-24 13:07 ` Ævar Arnfjörð Bjarmason
2010-09-24 14:42 ` Gustavo Narea
2010-09-24 15:33 ` Julian Phillips
2010-09-24 16:32 ` Joshua Jensen [this message]
2010-09-27 10:33 ` Gustavo Narea
2010-09-27 11:53 ` Martin Pettersson
2010-09-24 15:57 ` Jakub Narebski
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=4C9CD2B2.3030106@workspacewhiz.com \
--to=jjensen@workspacewhiz.com \
--cc=git@vger.kernel.org \
--cc=gnarea@tech.2degreesnetwork.com \
--cc=julian@quantumfyre.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.