unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: emacs-devel@gnu.org
Subject: Re: Emacs-devel Digest, Vol 44, Issue 41
Date: Mon, 8 Oct 2007 17:26:27 -0400	[thread overview]
Message-ID: <20071008212626.GA28553@thyrsus.com> (raw)
In-Reply-To: <20071007003329.B1DC47393F@grelber.thyrsus.com>

Stefan writes:
> In the latest vc.el I've seen you've used "current focus version", but I see
> no need for "focus" here (and I prefer "revision" to "version" here as
> well), so why not "current revision"?  It's a terminology that I've often
> seen used.

So have I, but I don't think it's specific enough.  Current with
respect to what?  It's too easy to look at "current revision" and
think it must refer to the head or tip version -- that is, what's
*chronologically* current as opposed to the version selected for
operation by the VCS, which might be anywhere in the history 
depending on how your did your last sync or tagging operation.

I actually share your preference for "revision" over "version", BTW.
But one thing at a time; let's get the logic merge done and save
things like performance tuning and bikeshedding about the terminology
for later.

> If you can slice your changes into several smaller patches, then that would
> be great, indeed.

I've committed a couple of patches that reduce the diff substantially 
without changing the existing logic.  I can do a bit more along that line,
but there is going to be at least one commit that will be *large*.

Dan Nicolaescu continues to be the hero of this effort; his review of
my latest version was, again, extremely helpful.  It gives me hope
that we can wrap up the logic merge within the next week or so.  

That would be good, as there is cleanup work -- like performance-tuning
VC-Dired -- that I want to get to, but is going to be too much of a
pain in the ass as long as the versions are still forked.  
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

       reply	other threads:[~2007-10-08 21:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071007003329.B1DC47393F@grelber.thyrsus.com>
2007-10-08 21:26 ` Eric S. Raymond [this message]
2007-10-09  2:29   ` Emacs-devel Digest, Vol 44, Issue 41 Stefan Monnier

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=20071008212626.GA28553@thyrsus.com \
    --to=esr@thyrsus.com \
    --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).