From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] clone: ignore --depth when cloning locally (implicitly --local)
Date: Thu, 26 Feb 2009 14:45:42 -0800 [thread overview]
Message-ID: <7v8wnsrf55.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1f63785d96d243ff19a063f684abbbe46cafc075.1235672273u.git.johannes.schindelin@gmx.de> (Johannes Schindelin's message of "Thu, 26 Feb 2009 19:20:19 +0100 (CET)")
Johannes Schindelin <johannes.schindelin@gmx.de> writes:
> When cloning locally, we default to --local, as it makes the whole
> operation fast and efficient.
>
> As the most common intent of cloning with a --depth parameter is to
> save space, and --local saves space more than --depth ever can,
> warn the user and ignore the --depth parameter when cloning locally.
>
> Should --depth be desired, the user can always force proper cloning
> by using a file:// URL.
>
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Makes sense. I'm inclined to apply this as a "fix" before 1.6.2, but I
cannot exactly say what we are fixing. User's expectations?
next prev parent reply other threads:[~2009-02-26 22:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1235672273u.git.johannes.schindelin@gmx.de>
2009-02-26 18:20 ` [PATCH] clone: ignore --depth when cloning locally (implicitly --local) Johannes Schindelin
2009-02-26 22:45 ` Junio C Hamano [this message]
2009-02-26 22:55 ` Johannes Schindelin
2009-02-26 23:31 ` [PATCH 0/2] shallow clone stuff Johannes Schindelin
2009-02-27 0:35 ` Junio C Hamano
2009-02-26 23:31 ` [PATCH 1/2] clone: do not ignore --no-hardlinks Johannes Schindelin
2009-02-27 2:58 ` Jeff King
2009-02-27 7:24 ` Junio C Hamano
2009-02-27 7:59 ` Junio C Hamano
2009-02-27 8:13 ` Junio C Hamano
2009-02-27 16:54 ` Daniel Barkalow
2009-02-27 11:35 ` Jeff King
2009-02-26 23:31 ` [PATCH 2/2] clone: ignore --depth when cloning locally (implicitly --local) Johannes Schindelin
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=7v8wnsrf55.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
/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.