all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: gnu-arch-users@gnu.org, emacs-devel@gnu.org
Subject: Re: cvs <-> arch mirroring scripts
Date: Mon, 18 Aug 2003 18:29:12 -0400	[thread overview]
Message-ID: <20030818222912.GC6940@fencepost> (raw)
In-Reply-To: <E19opU6-0006Cc-3z@fencepost.gnu.org>

On Mon, Aug 18, 2003 at 03:16:06PM -0400, Richard Stallman wrote:
>       Revision:     Identifies the arch changeset the change came from;
> 		    I think this is very useful information and should be
> 		    kept.
> 
> How is that useful to CVS users like me?

Because (1) it identifies which arch revision the change came from, which
allows you to go back to the arch changeset to get more info if you need it,
(2) it helps identify the change as part of a changeset along with other
files, which is a generally useful concept even if not supported by the
mechanics of CVS.

You may not immediately need this info in your everyday log browsing, but
that doesnt mean it's not useful.  However, it does suggest that maybe the
idea of adding output-filtering to vc.el's C-v l command is good.  That way
you can strip out this stuff that may interfere with casual browsing, but
it's available in case you ever _do_ want it.

>       Creator:      This is redundant in this case, but since CVS checkins
> 		    from arch probably will occur from a single `gateway user'
> 		    so that it's necessary to record the _actual_ author
> 		    somewhere.
> 
> 1. We should think of this person as the one who checked in the
> change.  If so, the info is useful but the CVS checkin user info is
> useless.  This name should go in the CVS checkin user name, not in a
> separate "Creator" field.

This is true.  I think modifying the `cvs' client to do such a
substitution would be a pain, but maybe this is another thing that vc.el
could easily do.

[Also note that this field could be used in other non-arch-related cases,
when for some reason one person checks in a change for another]

It looks to me like the best solution is simply to hack vc.el a bit as
previously described.

-Miles
-- 
Occam's razor split hairs so well, I bought the whole argument!


_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://mail.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/


  reply	other threads:[~2003-08-18 22:29 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
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 [this message]
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=20030818222912.GC6940@fencepost \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gnu-arch-users@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.