From: Bastien <bzg@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Let git ignore src/temacs* not just src/temacs
Date: Sat, 18 May 2019 20:23:15 +0200 [thread overview]
Message-ID: <87h89r7hbg.fsf@gnu.org> (raw)
In-Reply-To: <68708eab-a3a4-ce1c-099a-c7db3f94155e@cs.ucla.edu> (Paul Eggert's message of "Sat, 18 May 2019 10:29:16 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> Paul Eggert wrote:
>> Bastien wrote:
>>> Let me know if I can apply the following patch.
>>
>> Sure, that makes sense.
>
> Hmm, well, as Stefan points out it *used* to make sense, but nowadays
> it shouldn't be needed. Sorry about the noise.
Okay, point taken. Thanks,
--
Bastien
prev parent reply other threads:[~2019-05-18 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 14:49 [PATCH] Let git ignore src/temacs* not just src/temacs Bastien
2019-05-18 16:10 ` Stefan Monnier
2019-05-18 17:24 ` Paul Eggert
2019-05-18 17:29 ` Paul Eggert
2019-05-18 18:23 ` Bastien [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=87h89r7hbg.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=eggert@cs.ucla.edu \
--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 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).