From: Tay Ray Chuan <rctay89@gmail.com>
To: Daniel Johnson <computerdruid@gmail.com>
Cc: git@vger.kernel.org, "Kristian Høgsberg" <krh@redhat.com>
Subject: Re: [PATCH/RFC] fetch: allow command line --tags to override config
Date: Thu, 5 Aug 2010 17:56:05 +0800 [thread overview]
Message-ID: <AANLkTikf96RLfTq4Q6DAPesr6j70CJfT8vBzidJk42dE@mail.gmail.com> (raw)
In-Reply-To: <1280948202-17385-1-git-send-email-ComputerDruid@gmail.com>
Hi,
On Thu, Aug 5, 2010 at 2:56 AM, Daniel Johnson <computerdruid@gmail.com> wrote:
> Originally, if remote.<name>.tagopt was set, the --tags and option would
> have no effect when given to git fetch. So if
> tagopt="--no-tags"
>
> git fetch --tags
>
> would not actually fetch tags.
>
> This patch changes this behavior to only follow what is written in the
> config if there is no option passed by the command line.
>
> Signed-off-by: Daniel Johnson <ComputerDruid@gmail.com>
This is pretty confusing as it is. Could you please provide a patch
for the git-fetch documentation too?
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2010-08-05 9:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 18:56 [PATCH/RFC] fetch: allow command line --tags to override config Daniel Johnson
2010-08-05 9:56 ` Tay Ray Chuan [this message]
2010-08-06 13:54 ` [PATCH] Documentation: changes in the behavior of tagopt Daniel Johnson
2010-08-08 2:17 ` Tay Ray Chuan
2010-08-11 22:57 ` [RFC/PATCHv2] fetch: allow command line --tags to override config Daniel Johnson
2010-08-13 1:22 ` Junio C Hamano
2010-08-13 20:13 ` [RFC/PATCH] t5525: test the tagopt variable and that it can be overridden Daniel Johnson
2010-08-13 20:55 ` Ævar Arnfjörð Bjarmason
2010-08-13 21:27 ` [RFC/PATCHv2] " Daniel Johnson
2010-08-13 21:39 ` Ævar Arnfjörð Bjarmason
2010-08-14 21:32 ` Daniel Johnson
2010-08-14 21:37 ` Ævar Arnfjörð Bjarmason
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=AANLkTikf96RLfTq4Q6DAPesr6j70CJfT8vBzidJk42dE@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=computerdruid@gmail.com \
--cc=git@vger.kernel.org \
--cc=krh@redhat.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).