From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Leo <sdl.web@gmail.com>
Cc: emacs-pretest-bug@gnu.org, 2988@emacsbugs.donarmstrong.com
Subject: bug#2988: 23.0.92; Document 'ancestor' in ediff info
Date: Mon, 13 Apr 2009 22:10:33 -0400 [thread overview]
Message-ID: <jwvr5zwugsw.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <m1y6u42ks1.fsf@cam.ac.uk> (Leo's message of "Tue, 14 Apr 2009 00:31:26 +0100")
> The concept 'ancestor' in ediff info is undocumented. My suspicion is
> that it might be an outdated concept and there is a modern replacement.
AFAIK, it's not outdated. It's simply tied to the notion of 3-way diff,
which you apparently don't know about.
Stefan
next prev parent reply other threads:[~2009-04-14 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 23:31 bug#2988: 23.0.92; Document 'ancestor' in ediff info Leo
2009-04-14 2:10 ` Stefan Monnier [this message]
2009-04-18 13:53 ` Leo
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=jwvr5zwugsw.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=2988@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=sdl.web@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 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).