From: Jonathan Nieder <jrnieder@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
"Brandon Williams" <bmwill@google.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: [PATCH] clone: add a --no-tags option to clone without tags
Date: Tue, 25 Apr 2017 15:35:33 -0700 [thread overview]
Message-ID: <20170425223533.GL28740@aiede.svl.corp.google.com> (raw)
In-Reply-To: <20170418191553.15464-1-avarab@gmail.com>
Hi,
Ævar Arnfjörð Bjarmason wrote:
> Add a --no-tags option to "git clone" to clone without tags. Currently
> there's no easy way to clone a repository and end up with just a
> "master" branch via --single-branch, or track all branches and no
> tags. Now --no-tags can be added to "git clone" with or without
> --single-branch to clone a repository without tags.
Could --single-branch be made to imply --no-tags, like --depth implies
--single-branch? After all, all I wanted is that one branch, not some
tags.
Callers who really want the tags could still pass --tags to request
that.
Just thinking out loud,
Jonathan
prev parent reply other threads:[~2017-04-25 22:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 21:28 Is there a way to get 'git fetch --no-tags' semantics with 'git clone'? Ævar Arnfjörð Bjarmason
2017-04-18 19:15 ` [PATCH] clone: add a --no-tags option to clone without tags Ævar Arnfjörð Bjarmason
2017-04-18 21:06 ` Ævar Arnfjörð Bjarmason
2017-04-18 23:30 ` Brandon Williams
2017-04-19 1:38 ` Junio C Hamano
2017-04-19 5:32 ` Junio C Hamano
2017-04-19 14:38 ` [PATCH v2] " Ævar Arnfjörð Bjarmason
2017-04-25 22:45 ` Jonathan Nieder
2017-04-26 1:26 ` Junio C Hamano
2017-04-26 8:56 ` Ævar Arnfjörð Bjarmason
2017-04-25 22:35 ` Jonathan Nieder [this message]
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=20170425223533.GL28740@aiede.svl.corp.google.com \
--to=jrnieder@gmail.com \
--cc=avarab@gmail.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.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.
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).