all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: arch-users@lists.fifthvision.net, emacs-devel@gnu.org, miles@gnu.org
Subject: Re: cvs <-> arch mirroring scripts
Date: Mon, 18 Aug 2003 15:15:51 -0400	[thread overview]
Message-ID: <E19opTr-0006B4-ND@fencepost.gnu.org> (raw)
In-Reply-To: <070e01c364e6$e9c4cb70$6400000a@shakti> (rv@gnu.org)

    > That is 6 lines longer than normal.  The extra lines will make it
    > harder to scan the CVS log for relevant information.  Can you make
    > that any more compact?  Is all of it really necessary?

    Another possibility would require a change to the cvs command line (harder
    to justify to the wide world), but might be useful.

    Adding a -L (long listing, since -l is already taken) flag to `cvs log' to
    list lines that are marked as extensions.

We could also add such a feature to C-x v l, which might be
more convenient than changing CVS.

  reply	other threads:[~2003-08-18 19:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1060744673.2522.27.camel@columbia>
     [not found] ` <buo65l2facg.fsf@mcspd15.ucom.lsi.nec.co.jp>
     [not found]   ` <1060803518.28891.27.camel@columbia>
2003-08-14  9:35     ` [arch-users] Re: cvs <-> arch mirroring scripts Miles Bader
2003-08-14  9:46       ` Robert Collins
2003-08-14  9:59         ` Miles Bader
2003-08-17 17:29       ` Richard Stallman
2003-08-17 17:42         ` Rajesh Vaidheeswarran
2003-08-18 19:15           ` Richard Stallman [this message]
2003-08-19 14:38             ` [arch-users] " Rajesh Vaidheeswarran
2003-08-20 17:23               ` Richard Stallman
2003-08-22  8:17                 ` dhruva
2003-08-18  4:10         ` Miles Bader
2003-08-18 19:16           ` Richard Stallman
2003-08-18 22:29             ` Miles Bader
2003-08-20  2:43               ` Richard Stallman

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=E19opTr-0006B4-ND@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=arch-users@lists.fifthvision.net \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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.