From: "Samy Louis" <Samy.seif@go-eknowledge.com>
To: <git@vger.kernel.org>
Subject: duplicated Working tree
Date: Wed, 23 Mar 2011 13:03:15 +0200 [thread overview]
Message-ID: <002701cbe949$e957f050$bc07d0f0$@go-eknowledge.com> (raw)
Hi,
I have a strange problem and need your support if possible.
When I clone a remote GIT repository (LAN) to local machine, I get two
working folder one at the GIT local folder (normal) and the other in
original path of where the remote repository had been created before it was
cloned to remote network.
How can I overcome this issue to only have one local working folder.
Step to reproduce it:
1- Create a local GIT repo. (D:\repositoies\projectname)
2- Clone the GIT repo. to network path ( \\server\GIT\ projectname) use a
bare flag.
3- Clone the remote repo ( \\server\GIT\ projectname) to other machine in
path (C:\GIT\projectname) and create working tree
4- We will fine two working tree one at C:\GIT\projectname and the other at
D:\repositoies\projectname.
Thanks in advance .
Regards
Samy Louis
next reply other threads:[~2011-03-23 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 11:03 Samy Louis [this message]
2011-03-23 13:38 ` duplicated Working tree Michael J Gruber
2011-03-23 14:00 ` Samy Louis
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='002701cbe949$e957f050$bc07d0f0$@go-eknowledge.com' \
--to=samy.seif@go-eknowledge.com \
--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).