all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Eli Zaretskii <eliz@gnu.org>
Cc: john.b.mastro@gmail.com, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: Why looking-at-p works?
Date: Thu, 08 Mar 2018 21:33:47 +0100	[thread overview]
Message-ID: <87muzi9uj8.fsf@mbork.pl> (raw)
In-Reply-To: <84481B9D-4772-49EC-95ED-9841D894AF02@gnu.org>


On 2018-03-08, at 05:40, Eli Zaretskii <eliz@gnu.org> wrote:

> On March 8, 2018 6:20:17 AM GMT+02:00, Marcin Borkowski <mbork@mbork.pl> wrote:
>> 
>> On 2018-03-07, at 20:53, Eli Zaretskii <eliz@gnu.org> wrote:
>> 
>> >> From: Marcin Borkowski <mbork@mbork.pl>
>> >> Date: Wed, 07 Mar 2018 14:06:29 +0100
>> >> Cc: John Mastro <john.b.mastro@gmail.com>, Drew Adams
>> <drew.adams@oracle.com>
>> >> 
>> >> How about this patch?
>> >
>> > Thanks, I fixed this with a slightly different text, and I see no
>> need
>> > to change the doc string in eval.c.
>> 
>> Out of curiosity, where can I see your changes?
>
> On the release branch.

Thanks.

-- 
Marcin Borkowski
http://mbork.pl



  reply	other threads:[~2018-03-08 20:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06  7:57 Why looking-at-p works? Marcin Borkowski
2018-03-06 18:53 ` John Mastro
2018-03-06 20:42   ` Marcin Borkowski
2018-03-06 22:23     ` Drew Adams
2018-03-07  9:09       ` Marcin Borkowski
2018-03-07 13:06         ` Marcin Borkowski
2018-03-07 19:53           ` Eli Zaretskii
2018-03-08  4:20             ` Marcin Borkowski
2018-03-08  4:40               ` Eli Zaretskii
2018-03-08 20:33                 ` Marcin Borkowski [this message]
2018-03-06 23:17     ` Nick Dokos
     [not found] <mailman.10182.1520323093.27995.help-gnu-emacs@gnu.org>
2018-03-06  8:49 ` Emanuel Berg
2018-05-15  8:34   ` andlind
2018-05-15  8:49     ` tomas

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=87muzi9uj8.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=john.b.mastro@gmail.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 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.