From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git@vger.kernel.org, gitster@pobox.com
Subject: [PATCH 0/2] shallow clone stuff
Date: Fri, 27 Feb 2009 00:31:17 +0100 (CET) [thread overview]
Message-ID: <cover.1235690903u.git.johannes.schindelin@gmx.de> (raw)
In-Reply-To: <alpine.DEB.1.00.0902262352380.10279@pacific.mpi-cbg.de>
The first patch fixes the current bug that --no-hardlinks is not heeded,
and the second patch introduces the warning when cloning locally with a
--depth parameter.
Johannes Schindelin (2):
clone: do not ignore --no-hardlinks
clone: ignore --depth when cloning locally (implicitly --local)
Documentation/git-clone.txt | 4 ++++
builtin-clone.c | 5 ++++-
t/t5701-clone-local.sh | 14 ++++++++++++++
3 files changed, 22 insertions(+), 1 deletions(-)
next prev parent reply other threads:[~2009-02-26 23:31 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
2009-02-26 22:55 ` Johannes Schindelin
2009-02-26 23:31 ` Johannes Schindelin [this message]
2009-02-27 0:35 ` [PATCH 0/2] shallow clone stuff 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=cover.1235690903u.git.johannes.schindelin@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).