git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH v2 0/4] Deprecate "not allow as-is commit with i-t-a entries"
Date: Tue, 07 Feb 2012 08:41:58 -0800	[thread overview]
Message-ID: <7v8vke38a1.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1328618804-31796-1-git-send-email-pclouds@gmail.com> ("Nguyễn	Thái Ngọc Duy"'s message of "Tue, 7 Feb 2012 19:46:40 +0700")

Nguyễn Thái Ngọc Duy  <pclouds@gmail.com> writes:

>  - git-add.txt changes are removed. In the end all kinds of commit
>    behave the same way, not worth putting more explanation during the
>    transition.
>
>  - reword config text and warning text (or more precisely copy/paste
>    from Junio/Jonathan's words)
>
>  - Hard coded release numbers are removed. Now it's simply "in future".
>
>  - Step 2 may be too annoying. Users are warned on every commit if
>    commit.ignoreIntentToAdd is set. I think it's good because it keeps
>    config file clean, but people may think otherwise.

Ahh, thanks.

But when I said "let's admit that this is just fixing an UI mistake, no
configuration, no options", I really meant it.  Without the backward
compatiblity "For now please do not fix this bug for me and keep being
buggy until I get used to the non-buggy behaviour" fuss, which we never do
to any bugfix.

That is how we are planning to handle "git merge" update to spawn editor
in interactive session in the next release. There is no "Please keep the
buggy behaviour" option; only an environment variable to help when we
mistake a scripted use as interactive, whose support is not going away
because it is not about "until I get used to the new behaviour".

  parent reply	other threads:[~2012-02-07 16:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 12:46 [PATCH v2 0/4] Deprecate "not allow as-is commit with i-t-a entries" Nguyễn Thái Ngọc Duy
2012-02-07 12:46 ` [PATCH v2 1/4] cache-tree: update API to take abitrary flags Nguyễn Thái Ngọc Duy
2012-02-07 12:46 ` [PATCH v2 2/4] commit: introduce a config key to allow as-is commit with i-t-a entries Nguyễn Thái Ngọc Duy
2012-02-07 12:46 ` [PATCH v2 3/4] commit: turn commit.ignoreIntentToAdd to true by default Nguyễn Thái Ngọc Duy
2012-02-07 12:46 ` [PATCH v2 4/4] commit: remove commit.ignoreIntentToAdd, assume it's always true Nguyễn Thái Ngọc Duy
2012-02-07 16:41 ` Junio C Hamano [this message]
2012-02-07 19:55   ` [PATCH v2 0/4] Deprecate "not allow as-is commit with i-t-a entries" Junio C Hamano
2012-02-08  4:03   ` Nguyen Thai Ngoc Duy
2012-02-08 17:34     ` Junio C Hamano
2012-02-09  2:23       ` Nguyen Thai Ngoc Duy

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=7v8vke38a1.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.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.
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).