From: Jonathan Nieder <jrnieder@gmail.com>
To: Walter Bright <boost@digitalmars.com>
Cc: git@vger.kernel.org
Subject: Re: noob user, want checkins to all be forced to LF terminated lines
Date: Sat, 31 Jul 2010 15:38:20 -0500 [thread overview]
Message-ID: <20100731203820.GA1773@burratino> (raw)
In-Reply-To: <i30g2s$dpt$1@dough.gmane.org>
Walter Bright wrote:
> Why would "git clone" even exist if copying the directory works?
As Ilari said, it works remotely. It’s even faster than just copying
the directory (since it has to do less reading), and it only copies
the repository, not the work tree or .git/config, which may or may not
be what you want.
More importantly, the reason I mentioned it was this: if you clone
to make your first backup, you are more likely (when appropriate) to
use "git fetch" instead of rsync to update the backup afterwards.
And for that operation, "git fetch" is much more efficient.
Anyway, feel free to ignore this advice. "cp -a" works fine already
and is sometimes just the right thing to do.
Jonathan
next prev parent reply other threads:[~2010-07-31 20:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 4:23 noob user, want checkins to all be forced to LF terminated lines Walter Bright
2010-07-31 4:49 ` Jonathan Nieder
2010-07-31 5:14 ` Walter Bright
2010-07-31 5:39 ` Ilari Liusvaara
2010-07-31 5:45 ` Walter Bright
2010-07-31 5:57 ` Ilari Liusvaara
2010-07-31 6:24 ` Walter Bright
2010-07-31 15:12 ` David Aguilar
2010-07-31 5:44 ` Jonathan Nieder
2010-07-31 6:32 ` Walter Bright
2010-07-31 6:41 ` Ilari Liusvaara
2010-07-31 20:38 ` Jonathan Nieder [this message]
2010-07-31 20:51 ` Walter Bright
2010-08-03 23:56 ` Jay Soffian
2010-08-04 5:29 ` Will Palmer
2010-07-31 5:41 ` Miles Bader
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=20100731203820.GA1773@burratino \
--to=jrnieder@gmail.com \
--cc=boost@digitalmars.com \
--cc=git@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).