git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Samy Louis" <Samy.seif@go-eknowledge.com>
To: "'Michael J Gruber'" <git@drmicha.warpmail.net>
Cc: <git@vger.kernel.org>
Subject: RE: duplicated Working tree
Date: Wed, 23 Mar 2011 16:00:45 +0200	[thread overview]
Message-ID: <002801cbe962$b4d313f0$1e793bd0$@go-eknowledge.com> (raw)
In-Reply-To: <4D89F7C5.6000900@drmicha.warpmail.net>

Yes I created it in local machine before I clone it to the remote machine ,
but  the issue appears   when I clone the remote repo to another machine to
different path.
Samy

-----Original Message-----
From: Michael J Gruber [mailto:git@drmicha.warpmail.net] 
Sent: Wednesday, March 23, 2011 3:38 PM
To: Samy Louis
Cc: git@vger.kernel.org
Subject: Re: duplicated Working tree

Samy Louis venit, vidit, dixit 23.03.2011 12:03:
> 
> 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 .

Didn't you create a working tree at D:\repositoies\projectname in step 1
already?

Michael

      reply	other threads:[~2011-03-23 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 11:03 duplicated Working tree Samy Louis
2011-03-23 13:38 ` Michael J Gruber
2011-03-23 14:00   ` Samy Louis [this message]

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='002801cbe962$b4d313f0$1e793bd0$@go-eknowledge.com' \
    --to=samy.seif@go-eknowledge.com \
    --cc=git@drmicha.warpmail.net \
    --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).