all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: master 00149f18ea9: Support modifying VC change comments for Git
Date: Wed, 23 Oct 2024 17:47:50 +0800	[thread overview]
Message-ID: <87ttd39mm1.fsf@melete.silentflame.com> (raw)
In-Reply-To: <86r087dvqa.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 23 Oct 2024 12:17:17 +0300")

Hello,

On Wed 23 Oct 2024 at 12:17pm +03, Eli Zaretskii wrote:

> The values of the new option vc-allow-rewriting-published-history
> could have their mnemonic value improved (and also become more
> consistent with our practices elsewhere), if they were changed as
> follows:
>
>   nil (default): don't allow
>   ask: ask whether to allow
>   t: allow without asking
>
> The current values, where t means "ask for confirmation" and 'no-ask'
> allows without asking is IMO sub-optimal, because t usually means in
> Emacs "do something unconditionally".
>
> So I suggest to change the values as described above.

`ask' is nicer than `no-ask', indeed.  I am however keen to steer people
towards `ask'.  In addition to t often meaning "do something
conditionally", it often means "turn this on in the most common way"
even if the most common way is not the most permissive way.

I would be grateful for more opinions on how this option should look.
CCing Dmitry.

-- 
Sean Whitton



  reply	other threads:[~2024-10-23  9:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23  9:17 master 00149f18ea9: Support modifying VC change comments for Git Eli Zaretskii
2024-10-23  9:47 ` Sean Whitton [this message]
2024-10-23 19:40   ` Dmitry Gutov
2024-10-24  3:33     ` Sean Whitton
2024-10-24  5:50     ` Eli Zaretskii
2024-10-24  9:06       ` Sean Whitton
2024-10-24  9:32       ` Dmitry Gutov

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=87ttd39mm1.fsf@melete.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.