From: viresh kumar <viresh.kumar@st.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Andreas Ericsson <ae@op5.se>,
"kusmabite@gmail.com" <kusmabite@gmail.com>,
Jakub Narebski <jnareb@gmail.com>,
"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: Thu, 16 Jun 2011 14:25:19 +0530 [thread overview]
Message-ID: <4DF9C4F7.6020305@st.com> (raw)
In-Reply-To: <4DF9C3BA.8010106@viscovery.net>
On 06/16/2011 02:20 PM, Johannes Sixt wrote:
> Am 6/16/2011 5:33, schrieb viresh kumar:
>> > And i wanted just linux source on windows, i will not be creating any patches from
>> > windows. Just needed code for reference.
> If you only want to peek into the files, you don't need the files checked
> out. Just have them in a bare repository and use, e.g.,
>
> git show master:mm/vmalloc.c
>
> You can also use a sparse checkout to omit the questionable files from the
> checkout. See man git-read-tree.
Thanks. I am doing it this way only.
--
viresh
next prev parent reply other threads:[~2011-06-16 8:55 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
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 [this message]
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=4DF9C4F7.6020305@st.com \
--to=viresh.kumar@st.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=jnareb@gmail.com \
--cc=kusmabite@gmail.com \
--cc=shiraz.hashim@st.com \
--cc=vipin.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 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.