git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: js/no-pager-shorthand [was: What's cooking in git.git (Apr 2018, #04; Mon, 30)]
Date: Mon, 30 Apr 2018 21:17:41 +0200	[thread overview]
Message-ID: <918c69be-89ce-c66d-92ee-4821e9412793@kdbg.org> (raw)
In-Reply-To: <xmqq4ljtz87g.fsf@gitster-ct.c.googlers.com>

Am 30.04.2018 um 05:25 schrieb Junio C Hamano:
> * js/no-pager-shorthand (2018-04-25) 1 commit
>   - git: add -N as a short option for --no-pager
> 
>   "git --no-pager cmd" did not have short-and-sweet single letter
>   option. Now it does.
> 
>   Will merge to 'next'.

I consider your argument that -N is only an abbreviation for an 
unspecific "no" a valid one. So, I would like to be sure that we are not 
painting us into the wrong corner by squatting -N for --no-pager.

I find -P is not that bad after all.

-- Hannes

  parent reply	other threads:[~2018-04-30 19:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30  3:25 What's cooking in git.git (Apr 2018, #04; Mon, 30) Junio C Hamano
2018-04-30 15:33 ` SZEDER Gábor
2018-05-01 13:46   ` Johannes Schindelin
2018-05-02  3:59     ` Junio C Hamano
2018-05-02  6:53       ` Johannes Schindelin
2018-05-02 10:46         ` Junio C Hamano
2018-05-02  1:36   ` Junio C Hamano
2018-04-30 19:17 ` Johannes Sixt [this message]
2018-05-01 11:57   ` js/no-pager-shorthand [was: What's cooking in git.git (Apr 2018, #04; Mon, 30)] Johannes Schindelin
2018-05-01 14:58     ` Johannes Sixt
2018-05-01 18:10       ` Eric Sunshine
2018-05-02  1:43         ` js/no-pager-shorthand [ Junio C Hamano
2018-05-01 18:46     ` js/no-pager-shorthand [was: What's cooking in git.git (Apr 2018, #04; Mon, 30)] Ævar Arnfjörð Bjarmason
2018-05-02 23:17 ` What's cooking in git.git (Apr 2018, #04; Mon, 30) Brandon Williams
2018-05-04 18:04 ` Elijah Newren
2018-05-07  4:39   ` Junio C Hamano

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=918c69be-89ce-c66d-92ee-4821e9412793@kdbg.org \
    --to=j6t@kdbg.org \
    --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. 
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).