unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andre Spiegel <spiegel@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: patch for documentation about version control
Date: Thu, 11 Nov 2004 12:55:17 +0100	[thread overview]
Message-ID: <1100174117.3428.194.camel@localhost> (raw)
In-Reply-To: <jkr7n14pu2.fsf@glug.org>

On Wed, 2004-11-10 at 11:43 -0500, Thien-Thi Nguyen wrote:

> as you can see, the patch does not actually change anything currently
> defined in vc-rcs.el; it is purely additive.  btw, ORIG => 1.41.  if
> there is a better way to get a file's per-line version info w/o parsing
> the masterfile, please let me know in the next few days.

It is fine to read information directly from the RCS master file, VC has
been doing that all along.  What about the efficiency of your parser,
though?  How long does it take to construct this full parse tree for a
large RCS master with many revisions?

Since we do need the line-by-line information, I guess there's not much
else we can do except to go for this full parse tree.

The code needs to be better commented.  It needs to explain in readable
English what you are doing at least in each major step.  "korg / grok /
decorate" is not enough.  This comment:

  ;; cvs envy (for now -- usurpers enjoy the dish best served cold)

is also not particularly helpful.

Finally, some of your variable names need to be improved.  A name like
"p-act-ract" or "r/d/a" is worse than a single-letter identifier because
the reader is left wondering what at all you are talking about.  Please
give meaningful names at least to these two variables/properties.

Please send me an updated version of your patch.  There is no need to do
this via emacs-devel, we can sort this out in personal mail.

Thanks for working on this; having vc-annotate work with RCS will be a
very worthwhile improvement.

  reply	other threads:[~2004-11-11 11:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09  6:55 patch for documentation about version control Alex Ott
2004-11-09  9:13 ` Andre Spiegel
2004-11-12  9:11   ` Alex Ott
2004-11-09 18:21 ` Karl Fogel
2004-11-09 21:32   ` Stefan Monnier
2004-11-09 21:34   ` Stefan Monnier
2004-11-09 22:09     ` David Kastrup
2004-11-10  9:00     ` Thien-Thi Nguyen
2004-11-10  9:22       ` Andre Spiegel
2004-11-10 16:43         ` Thien-Thi Nguyen
2004-11-11 11:55           ` Andre Spiegel [this message]
2004-11-11 15:11             ` Stefan
2004-11-11 15:36               ` Andre Spiegel
2004-11-11 15:25             ` Thien-Thi Nguyen
2004-11-11 16:06             ` Thien-Thi Nguyen
2004-11-11 18:25             ` Thien-Thi Nguyen
2004-11-11 20:59               ` Andre Spiegel
2004-11-12  9:33                 ` Thien-Thi Nguyen
2004-11-10  9:30     ` Andre Spiegel

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=1100174117.3428.194.camel@localhost \
    --to=spiegel@gnu.org \
    --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).