git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: viresh kumar <viresh.kumar@st.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	Shiraz HASHIM <shiraz.hashim@st.com>,
	Vipin KUMAR <vipin.kumar@st.com>
Subject: Re: Copying Git repository from Linux to Windows.
Date: Wed, 15 Jun 2011 11:47:34 +0200	[thread overview]
Message-ID: <4DF87FB6.2080503@op5.se> (raw)
In-Reply-To: <4DF87B42.1020004@st.com>

On 06/15/2011 11:28 AM, viresh kumar wrote:
> Hello,
> 
> I wanted to copy my complete Linux GIT repo from Linux PC to Windows. I also wanted everything
> related to remote branches too, so need to copy and clone and fetch wouldn't work.
> 
> I don't have windows on same network, so i need to copy to memory stick and then to Windows PC.
> 
> After completing copy operation on mem stick, i found something strange.
> - git branch shows correct results and is exactly same of state at Linux machine.
> - git log is also fine.
> - git status, shows me a lot of files are modified, which is not present in Linux.
> - git reset --hard also doesn't work and fails with following error.
> 
> 
> $ git reset --hard HEAD
> error: unable to create symlink arch/microblaze/boot/dts/system.dts (Operation not permitted)
> Checking out files: 100% (36696/36696), done.
> fatal: Could not reset index file to revision 'HEAD'.
> 
> 
> Any help about this issue would be very helpful.
> 

The Linux kernel repository isn't very good to work with on Windows
machines, or anywhere where the filesystem is either case-insensitive
or case-agnostic.

One reason is that it contains symlink. The other is that there are
files sharing the same name and only differ in case.

I suppose the main thought behind it is that Linux kernel hackers
almost exclusively use Linux (which has sane filesystems) to do
their work, so it hasn't been rectified in the 5 or so years it has
been a known (non-)problem.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

  reply	other threads:[~2011-06-15  9:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15  9:28 Copying Git repository from Linux to Windows viresh kumar
2011-06-15  9:47 ` Andreas Ericsson [this message]
2011-06-15 10:40 ` Jakub Narebski
2011-06-15 11:04   ` viresh kumar
2011-06-15 11:26     ` Erik Faye-Lund
2011-06-15 12:02       ` viresh kumar
2011-06-15 12:41         ` Andreas Ericsson
2011-06-16  3:33           ` viresh kumar
2011-06-16  8:17             ` Philippe Vaucher
2011-06-16  8:22               ` viresh kumar
2011-06-16  8:50             ` Johannes Sixt
2011-06-16  8:55               ` viresh kumar
2011-06-16 14:15             ` Jakub Narebski
2011-06-17  3:52               ` viresh kumar
2011-06-15 14:14         ` Jakub Narebski
2011-06-20 19:57           ` Phil Hord
2011-06-15 11:29     ` 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=4DF87FB6.2080503@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=shiraz.hashim@st.com \
    --cc=vipin.kumar@st.com \
    --cc=viresh.kumar@st.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).