git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] advice: Add advice.scissors to suppress "do not modify or remove this line"
Date: Tue, 16 Apr 2024 13:35:41 -0700	[thread overview]
Message-ID: <xmqq7cgxdp0i.fsf@gitster.g> (raw)
In-Reply-To: <Zh7NZhB1n2o1k7jI@localhost> (Josh Triplett's message of "Tue, 16 Apr 2024 20:11:34 +0100")

Josh Triplett <josh@joshtriplett.org> writes:

> On Sun, Feb 25, 2024 at 08:21:54PM -0800, Josh Triplett wrote:
>> The scissors line before the diff in a verbose commit, or above all the
>> comments when using --cleanup=scissors, has the following two lines of
>> explanation after it:
>> 
>> Do not modify or remove the line above.
>> Everything below it will be ignored.
>> 
>> This is useful advice for new users, but potentially redundant for
>> experienced users, who might instead appreciate seeing two more lines of
>> information in their editor.
>> 
>> Add advice.scissors to suppress that explanation.
>
> Following up on this patch. Happy to rework if needed.

I am not personally interested in the feature myself, and I doubt it
would help the end-user experience very much.  You'd need to find
somebody else to cheer for the topic ;-)

Thanks.



  reply	other threads:[~2024-04-16 20:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26  4:21 [PATCH] advice: Add advice.scissors to suppress "do not modify or remove this line" Josh Triplett
2024-04-16 19:11 ` Josh Triplett
2024-04-16 20:35   ` Junio C Hamano [this message]
2024-04-16 20:44     ` rsbecker
2024-04-16 22:31       ` Junio C Hamano
2024-04-16 22:52         ` rsbecker
2024-04-17  4:00         ` Dragan Simic
2024-04-16 20:28 ` Rubén Justo

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=xmqq7cgxdp0i.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=josh@joshtriplett.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 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).