From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Switching from old git tree
Date: Sat, 15 Nov 2014 10:18:19 +0100 [thread overview]
Message-ID: <87d28oom90.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 83zjbsg7qz.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Kenneth Raeburn <raeburn@raeburn.org>
>> Date: Sat, 15 Nov 2014 03:43:05 -0500
>>
>> After creating your "main" clone of the new upstream repository,
>> clone *that* one locally (use the "-s" option to save disk space)
>
> Careful: kids are listening! The -s option to clone has a caveat on
> its man page, which, to me sounds as "Kids, don't try this at home!"
-s does not save disk space over the default _unless_ your local clone
happens to be on a different file system. There is little reason to
keep local clones on different file systems, however. On the same file
system, the normal git clone operation uses hard links, and those are
unproblematic regarding the given caveat.
--
David Kastrup
next prev parent reply other threads:[~2014-11-15 9:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 11:26 Switching from old git tree Peder O. Klingenberg
2014-11-14 12:20 ` David Kastrup
2014-11-14 12:35 ` Sven Axelsson
2014-11-14 12:38 ` Sven Axelsson
2014-11-14 13:21 ` Peder O. Klingenberg
2014-11-14 13:53 ` David Kastrup
2014-11-14 14:20 ` Sven Axelsson
2014-11-14 14:54 ` David Kastrup
2014-11-14 15:52 ` Andreas Schwab
2014-11-14 18:29 ` David Caldwell
2014-11-15 8:43 ` Kenneth Raeburn
2014-11-15 8:58 ` Eli Zaretskii
2014-11-15 9:18 ` David Kastrup [this message]
2014-11-15 9:55 ` Eli Zaretskii
2014-11-15 18:26 ` Ken Raeburn
2014-11-14 13:29 ` Nicolas Richard
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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d28oom90.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).