From: Chuck Lever <cel@citi.umich.edu>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [howto] Kernel hacker's guide to git, updated
Date: Thu, 29 Sep 2005 17:23:00 -0400 [thread overview]
Message-ID: <433C5B34.9060907@citi.umich.edu> (raw)
In-Reply-To: <433C4B6D.6030701@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
Jeff Garzik wrote:
> Dave Jones wrote:
>
>> You wrote..
>>
>> $ git clone
>> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>> linux-2.6
>> $ cd linux-2.6
>> $ rsync -a --verbose --stats --progress \
>>
>> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/
>> \
>> .git/
>>
>> Could be just..
>>
>> $ git clone
>> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>> linux-2.6
>> $ cd linux-2.6
>> $ git pull
>>
>> Likewise, in the next section, git pull doesn't need an argument
>> if pulling from the repo it cloned.
>
>
>
> Nope. It intentionally includes the manual rsync because clone/pull
> doesn't seem to grab tags. Or at least last time I checked...
i just used the instructions at the bottom of your web page to grab new
tags, and it completely wiped all my Stacked Git metadata. (fortunately
i was trying this in a test repository, and it will be simple to recover
the missing files).
so, this is probably something that should have a warning, or maybe you
might consider providing an example that won't wipe out existing files
and directories under .git/ ...
[-- Attachment #2: cel.vcf --]
[-- Type: text/x-vcard, Size: 439 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Charles
org:Network Appliance, Incorporated;Linux NFS Client Development
adr:535 West William Street, Suite 3100;;Center for Information Technology Integration;Ann Arbor;MI;48103-4943;USA
email;internet:cel@citi.umich.edu
title:Member of Technical Staff
tel;work:+1 734 763 4415
tel;fax:+1 734 763 4434
tel;home:+1 734 668 1089
x-mozilla-html:FALSE
url:http://www.monkey.org/~cel/
version:2.1
end:vcard
prev parent reply other threads:[~2005-09-29 21:23 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 11:03 [howto] Kernel hacker's guide to git, updated Jeff Garzik
2005-09-29 15:18 ` David Leimbach
2005-09-29 16:03 ` Alberto Patino
2005-09-29 16:13 ` David Leimbach
2005-09-29 19:08 ` Oliver Neukum
2005-09-29 19:34 ` Jon Loeliger
2005-09-29 19:38 ` Oliver Neukum
2005-09-30 7:37 ` Junio C Hamano
2005-09-30 8:36 ` Oliver Neukum
2005-09-30 16:39 ` Linus Torvalds
2005-09-29 20:02 ` Dave Jones
2005-09-29 20:07 ` Anton Altaparmakov
2005-09-29 20:11 ` Dave Jones
2005-09-29 21:14 ` Linus Torvalds
2005-09-29 21:26 ` Linus Torvalds
2005-09-29 21:33 ` Dave Jones
2005-09-29 21:55 ` Linus Torvalds
2005-09-29 22:12 ` Anton Altaparmakov
2005-09-29 22:25 ` Linus Torvalds
2005-09-29 22:32 ` Anton Altaparmakov
2005-09-29 23:19 ` Junio C Hamano
2005-09-30 12:22 ` Johannes Schindelin
2005-09-29 23:17 ` Horst von Brand
2005-09-30 0:47 ` Linus Torvalds
2005-09-30 1:54 ` Junio C Hamano
2005-09-30 2:36 ` Linus Torvalds
2005-10-01 0:10 ` Linus Torvalds
2005-10-01 1:58 ` Horst von Brand
2005-10-03 1:03 ` Linus Torvalds
2005-09-29 21:33 ` Elfyn McBratney
2005-09-29 21:35 ` Linus Torvalds
2005-09-29 21:40 ` Dave Jones
2005-09-29 20:15 ` Jeff Garzik
2005-09-29 21:04 ` Junio C Hamano
2005-09-30 11:15 ` Jeff Garzik
2005-09-30 11:55 ` Junio C Hamano
2005-09-30 14:11 ` Jeff Garzik
2005-10-02 8:47 ` Junio C Hamano
2005-09-30 18:14 ` Linus Torvalds
2005-10-01 7:36 ` Junio C Hamano
2005-09-30 12:02 ` Oliver Neukum
2005-09-30 13:58 ` Jeff Garzik
2005-09-30 15:10 ` Alberto Patino
2005-09-30 12:07 ` Erik Mouw
2005-09-30 14:08 ` Jeff Garzik
2005-09-30 18:13 ` Horst von Brand
2005-10-01 0:17 ` Jeff Garzik
2005-09-30 22:52 ` Francois Romieu
2005-09-29 21:23 ` Chuck Lever [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=433C5B34.9060907@citi.umich.edu \
--to=cel@citi.umich.edu \
--cc=git@vger.kernel.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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).