unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Spencer Baugh <sbaugh@janestreet.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sbaugh@catern.com, monnier@iro.umontreal.ca, 64071@debbugs.gnu.org
Subject: bug#64071: 28.2; smerge-diff creates *vc-diff* without setting it up
Date: Wed, 04 Oct 2023 10:05:26 -0400	[thread overview]
Message-ID: <ierfs2qv5y1.fsf@janestreet.com> (raw)
In-Reply-To: <83cyzjyz8r.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 19 Aug 2023 15:48:20 +0300")

Eli Zaretskii <eliz@gnu.org> writes:
>> From: sbaugh@catern.com
>> Date: Sat, 19 Aug 2023 12:32:01 +0000 (UTC)
>> Cc: Spencer Baugh <sbaugh@janestreet.com>, monnier@iro.umontreal.ca,
>> 	64071@debbugs.gnu.org
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> >> From: Spencer Baugh <sbaugh@janestreet.com>
>> >> Cc: monnier@iro.umontreal.ca,  64071@debbugs.gnu.org
>> >> Date: Wed, 28 Jun 2023 08:48:38 -0400
>> >> 
>> >> > See above: we shouldn't change the read-only attribute that was set by
>> >> > the user.
>> >> 
>> >> Good point.  How about this?
>> >
>> > Better, thanks.
>> 
>> Is this patch OK to apply, then?
>
> Yes, I think so.

Could it be applied, then?





  reply	other threads:[~2023-10-04 14:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 21:41 bug#64071: 28.2; smerge-diff creates *vc-diff* without setting it up Spencer Baugh
2023-06-15  7:20 ` Eli Zaretskii
2023-06-27 20:17   ` Spencer Baugh
2023-06-28 11:41     ` Eli Zaretskii
2023-06-28 12:48       ` Spencer Baugh
2023-06-28 12:58         ` Eli Zaretskii
2023-08-19 12:32           ` sbaugh
2023-08-19 12:48             ` Eli Zaretskii
2023-10-04 14:05               ` Spencer Baugh [this message]
2023-10-05  8:06                 ` Eli Zaretskii
2023-06-15 15:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ierfs2qv5y1.fsf@janestreet.com \
    --to=sbaugh@janestreet.com \
    --cc=64071@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=sbaugh@catern.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://git.savannah.gnu.org/cgit/emacs.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).