From: Linus Torvalds <torvalds@osdl.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Paolo Ornati <ornati@fastwebnet.it>, linux-kernel@vger.kernel.org
Subject: Re: Linux v2.6.16-c2
Date: Fri, 3 Feb 2006 13:01:04 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602031258300.4630@g5.osdl.org> (raw)
In-Reply-To: <43E3BF5A.3040305@lwfinger.net>
On Fri, 3 Feb 2006, Larry Finger wrote:
> Paolo Ornati wrote:
> > On Fri, 03 Feb 2006 12:25:05 -0600
> > Larry Finger <Larry.Finger@lwfinger.net> wrote:
> >
> >
> > > Thanks for the explanation. I have to admit that git is pretty much a
> > > black box to me. I use the guide at http://linux.yyz.us/git-howto.html and
> > > it recommends using rsync. I'll have to figure out how to change to git
> > > protocol.
> >
> >
> > Just do:
> >
> > git pull
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> >
> > :)
> >
>
> Got it now. Thanks.
You can also edit the file that describe your shorthand notation. If you
normally do "git pull origin" just look into the ".git/remotes/origin"
file, and I think you'll find it very obvious what it all does.
(If you used a really old version of git to create the archive originally,
it might be ".git/branches/origin" instead).
Linus
next prev parent reply other threads:[~2006-02-03 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 17:56 Larry Finger
2006-02-03 18:11 ` Linus Torvalds
2006-02-03 18:25 ` Larry Finger
2006-02-03 19:57 ` Paolo Ornati
2006-02-03 20:38 ` Larry Finger
2006-02-03 21:01 ` Linus Torvalds [this message]
2006-02-03 21:11 ` Larry Finger
2006-02-03 23:50 ` Ryan Anderson
2006-02-03 23:59 ` Linus Torvalds
2006-02-04 0:35 ` Diego Calleja
2006-02-04 2:16 ` Linus Torvalds
2006-02-04 14:14 ` Diego Calleja
-- strict thread matches above, loose matches on Subject: below --
2006-02-03 6:36 Linus Torvalds
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=Pine.LNX.4.64.0602031258300.4630@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@fastwebnet.it \
/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
all inboxes | Powered by JetHome®