From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git 1.7.10-rc0
Date: Thu, 8 Mar 2012 17:29:16 +0700 [thread overview]
Message-ID: <CACsJy8CYTnrcAX6TNORdg=KAk4_xNupT11Uw8o8gnW6NtQtMCA@mail.gmail.com> (raw)
In-Reply-To: <7v7gyvkh84.fsf@alter.siamese.dyndns.org>
On Thu, Mar 8, 2012 at 8:35 AM, Junio C Hamano <gitster@pobox.com> wrote:
> * "git clone" learned "--single-branch" option to limit cloning to a
> single branch (surprise!).
--single-branch also limits fetching tags to minimum, I'm not sure we
need to mention that. It may be a good idea to mention "shallow clone"
or --depth, where this feature is most beneficial, to catch people's
eyes if they are interested in shallow clone.
--
Duy
next prev parent reply other threads:[~2012-03-08 10:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 1:35 [ANNOUNCE] Git 1.7.10-rc0 Junio C Hamano
2012-03-08 6:30 ` Jeff King
2012-03-08 6:42 ` Junio C Hamano
2012-03-08 6:46 ` Junio C Hamano
2012-03-08 6:53 ` Jeff King
2012-03-08 19:55 ` Junio C Hamano
2012-03-08 8:54 ` [PATCH 1/2] perf: load test-lib-functions from the correct directory Thomas Rast
2012-03-08 8:54 ` [PATCH 2/2] perf: export some important test-lib variables Thomas Rast
2012-09-17 13:15 ` Ramkumar Ramachandra
2012-03-08 10:17 ` [ANNOUNCE] Git 1.7.10-rc0 Thomas Rast
2012-03-08 10:29 ` Nguyen Thai Ngoc Duy [this message]
2012-03-08 19:55 ` Junio C Hamano
2012-03-08 10:42 ` Jakub Narebski
2012-03-08 16:28 ` Junio C Hamano
2012-03-08 16:55 ` Jakub Narebski
2012-03-08 20:05 ` Junio C Hamano
2012-03-08 13:18 ` Tim Henigan
2012-03-08 20:07 ` Junio C Hamano
2012-03-09 13:35 ` [PATCH] RelNotes: noted the addition of contrib/diffall Tim Henigan
2012-03-09 18:15 ` Junio C Hamano
2012-03-09 18:41 ` Tim Henigan
2012-03-08 15:17 ` [ANNOUNCE] Git 1.7.10-rc0 Marc Branchaud
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8CYTnrcAX6TNORdg=KAk4_xNupT11Uw8o8gnW6NtQtMCA@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).