git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: jn/shell-disable-interactive (Re: What's cooking in git.git (Feb 2013, #05; Tue, 12))
Date: Tue, 12 Feb 2013 16:12:13 -0800	[thread overview]
Message-ID: <20130213001213.GA15246@google.com> (raw)
In-Reply-To: <7v621xdql8.fsf@alter.siamese.dyndns.org>

Junio C Hamano wrote:

> * jn/shell-disable-interactive (2013-02-11) 2 commits
>  - shell: pay attention to exit status from 'help' command
>  - shell doc: emphasize purpose and security model
>
>  Will merge to 'next'.

Please hold off on merging the second patch.  I'd like to reroll
renaming the command to 'no-interactive-login' or some such, which
would be less disruptive to existing setups and should be easier to
explain.

Thanks,
Jonathan

  reply	other threads:[~2013-02-13  0:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13  0:06 What's cooking in git.git (Feb 2013, #05; Tue, 12) Junio C Hamano
2013-02-13  0:12 ` Jonathan Nieder [this message]
2013-02-13  0:15   ` jn/shell-disable-interactive (Re: What's cooking in git.git (Feb 2013, #05; Tue, 12)) Junio C Hamano
2013-02-13  0:21 ` What's cooking in git.git (Feb 2013, #05; Tue, 12) Andrew Ardill
2013-02-13  0:34   ` Junio C Hamano
2013-02-13  0:42     ` Andrew Ardill
2013-02-13 15:27       ` Junio C Hamano
2013-02-14  2:43         ` Andrew Ardill
2013-02-14  4:36           ` Junio C Hamano
2013-02-14  4:54             ` Andrew Ardill
2013-02-14 16:59               ` Junio C Hamano
2013-02-14 23:17                 ` Junio C Hamano
2013-02-22  8:32                   ` Miles Bader
2013-02-22 16:58                     ` Junio C Hamano
2013-02-18 20:21 ` greened

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=20130213001213.GA15246@google.com \
    --to=jrnieder@gmail.com \
    --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. 
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).