all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, 27764-done@debbugs.gnu.org
Cc: "27764@debbugs.gnu.org" <27764@debbugs.gnu.org>
Subject: bug#27764: 26.0.50; Argument STARTUP-HOOKS for `ediff-files' undocumented
Date: Sun, 05 Nov 2017 17:54:47 +0000	[thread overview]
Message-ID: <CAArVCkS92J55wJs0b5Wa7_On_N36M5Vw6+9QN2vN5GOspDWVRg@mail.gmail.com> (raw)
In-Reply-To: <834lq8u0rg.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

Eli Zaretskii <eliz@gnu.org> schrieb am So., 5. Nov. 2017 um 17:51 Uhr:

> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Sun, 05 Nov 2017 16:29:35 +0000
> > Cc: 27764@debbugs.gnu.org
> >
> >  Can we have there at least the list of the symbols that are seen in
> >  the sources:  I see these:
> >
> >   ediff-merge-files-with-ancestor, ediff-last-dir-ancestor,
> >   ediff-last-dir-C, ediff-buffers, ediff-buffers3, ediff-merge-buffers,
> >   ediff-merge-buffers-with-ancestor
> >
> >  If this list is too long to be repeated in each doc string, we could
> >  have it once, and reference that place from the other do strings.  I
> >  think either way would be much better than using some generic text.
> >
> > Here's a new version of the patch.
>
> Thanks, this is fine.
>

Thanks, pushed as 72d07d1950 to the release branch.

[-- Attachment #2: Type: text/html, Size: 1357 bytes --]

      reply	other threads:[~2017-11-05 17:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19  9:20 bug#27764: 26.0.50; Argument STARTUP-HOOKS for `ediff-files' undocumented Philipp Stephani
2017-09-23 18:46 ` Philipp Stephani
2017-09-23 18:59   ` Eli Zaretskii
2017-09-24  8:00     ` Philipp Stephani
2017-09-29  7:17       ` Eli Zaretskii
2017-11-05 16:29         ` Philipp Stephani
2017-11-05 16:51           ` Eli Zaretskii
2017-11-05 17:54             ` Philipp Stephani [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

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

  git send-email \
    --in-reply-to=CAArVCkS92J55wJs0b5Wa7_On_N36M5Vw6+9QN2vN5GOspDWVRg@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=27764-done@debbugs.gnu.org \
    --cc=27764@debbugs.gnu.org \
    --cc=eliz@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 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.