From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Bert Wesarg <bert.wesarg@googlemail.com>, git@vger.kernel.org
Subject: Re: [PATCH] doc: clarify "explicitly given" in push.default
Date: Tue, 28 Jan 2020 21:21:32 -0800 [thread overview]
Message-ID: <xmqq7e1a7s83.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20200129024124.GC596379@coredump.intra.peff.net> (Jeff King's message of "Tue, 28 Jan 2020 21:41:24 -0500")
Jeff King <peff@peff.net> writes:
> Though I'd still slightly worry that somebody might not consider
> configured refspecs. Saying more clearly "any refspec no matter where it
> comes from" might still be worthwhile. I.e., something like:
>
> Defines the action `git push` should take if no refspec is given
> (whether from the command-line, config, or elsewhere).
That's 100x better than to say "explicit" "implicit" etc. and then
have readers guess what the adjectives mean or explain what they
mean in (parentheses).
next prev parent reply other threads:[~2020-01-29 5:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 20:29 [Q] push refspec with wildcard pushes all matching branches Bert Wesarg
2020-01-25 0:38 ` Jeff King
2020-01-25 7:38 ` Bert Wesarg
2020-01-25 20:05 ` [PATCH] doc: clarify "explicitly given" in push.default Jeff King
2020-01-27 7:00 ` Bert Wesarg
2020-01-27 7:02 ` Jeff King
2020-01-27 9:25 ` Bert Wesarg
2020-01-27 23:12 ` Jeff King
2020-01-28 22:11 ` Junio C Hamano
2020-01-29 2:41 ` Jeff King
2020-01-29 5:21 ` Junio C Hamano [this message]
2020-01-29 5:53 ` Jeff King
2020-01-27 19:48 ` Bert Wesarg
2020-01-27 20:53 ` Bert Wesarg
2020-01-27 23:14 ` Jeff King
2020-01-28 20:48 ` Bert Wesarg
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=xmqq7e1a7s83.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).