From: Nick Andrew <nick@nick-andrew.net>
To: rdkrsr <rdkrsr@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: Fwd: after first git clone of linux kernel repository there are changed files in working dir
Date: Sat, 13 Dec 2008 00:51:34 +1100 [thread overview]
Message-ID: <20081212135134.GA18814@mail.local.tull.net> (raw)
In-Reply-To: <d304880b0812110958u3da52e4fs7e5154ebe9a353a@mail.gmail.com>
On Thu, Dec 11, 2008 at 06:58:01PM +0100, rdkrsr wrote:
> windows xp and msysgit for this. And the file system is NTFS. I'm
> using dual boot to sporadicly use linux and tried also linux in
> virtual box.
You could use git inside your VirtualBox linux install.
> But both isn't really good. Maybe one day I dare to use
> linux as my primary OS.
It's not scary, really.
Nick.
next prev parent reply other threads:[~2008-12-12 13:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d304880b0812101019ufe85095h46ff0fe00d32bbd0@mail.gmail.com>
2008-12-10 18:22 ` after first git clone of linux kernel repository there are changed files in working dir rdkrsr
2008-12-10 20:20 ` Brett Simmers
[not found] ` <d304880b0812110142g41b80745ic09a7200e02dcdb0@mail.gmail.com>
2008-12-11 17:15 ` Fwd: " rdkrsr
2008-12-11 17:41 ` Linus Torvalds
2008-12-11 17:58 ` rdkrsr
2008-12-11 20:23 ` Boyd Stephen Smith Jr.
2008-12-11 20:35 ` Giuseppe Bilotta
2008-12-12 13:51 ` Nick Andrew [this message]
2009-01-19 13:36 ` Hannu Koivisto
2009-01-19 23:52 ` An idea: maybe Git should use a lock/unlock file mode for problematic files? [Was: Re: after first git clone of linux kernel repository there are changed files in working dir] thestar
2009-01-20 20:11 ` Daniel Barkalow
2009-01-20 21:28 ` John Chapman
2009-01-20 22:08 ` Daniel Barkalow
2009-01-20 23:25 ` Alex Riesen
2009-01-21 0:03 ` Daniel Barkalow
2009-01-21 7:25 ` Alex Riesen
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081212135134.GA18814@mail.local.tull.net \
--to=nick@nick-andrew.net \
--cc=git@vger.kernel.org \
--cc=rdkrsr@googlemail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).