unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>
Cc: dmitry@gutov.dev, 64266-done@debbugs.gnu.org, sbaugh@catern.com
Subject: bug#64266: [PATCH] ; * lisp/progmodes/project.el (project-current): Doc fix.
Date: Thu, 13 Jul 2023 09:15:51 +0300	[thread overview]
Message-ID: <83bkgg5obs.fsf@gnu.org> (raw)
In-Reply-To: <m1edlhqzza.fsf@eshelyaron.com> (message from Eshel Yaron on Sun,  09 Jul 2023 10:57:13 +0300)

> From: Eshel Yaron <me@eshelyaron.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,  64266@debbugs.gnu.org, sbaugh@catern.com
> Date: Sun, 09 Jul 2023 10:57:13 +0300
> 
> Dmitry Gutov <dmitry@gutov.dev> writes:
> 
> > On 24/06/2023 20:06, Eli Zaretskii wrote:
> >> I would recommend waiting for Dmitry and Spencer to chime in, and
> >> submit a followup after their comments, if any.
> >
> > Your suggested versions sounds good to me too, thanks.
> 
> Thanks, I'm attaching an updated patch following Eli's wording.
> 
> Also CC'ing Spencer in case there are further comments.

Thanks, installed on the master branch, and closing the bug.





      parent reply	other threads:[~2023-07-13  6:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 14:35 bug#64266: [PATCH] ; * lisp/progmodes/project.el (project-current): Doc fix Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-24 15:01 ` Eli Zaretskii
2023-06-24 15:32   ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-24 17:06     ` Eli Zaretskii
2023-06-25  2:20       ` Dmitry Gutov
2023-07-09  7:57         ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-09 13:19           ` sbaugh
2023-07-13  6:15           ` Eli Zaretskii [this message]

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=83bkgg5obs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64266-done@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=me@eshelyaron.com \
    --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).