From: Miles Bader <miles@lsi.nec.co.jp>
Subject: Re: Moving files from lisp/gnus/ to lisp/net/?
Date: Thu, 21 Oct 2004 10:28:52 +0900 [thread overview]
Message-ID: <buopt3cq2p7.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <m31xftwrp8.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 20 Oct 2004 13:32:19 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> I think this is generally considered a very bad thing to do. It's much safer
>> (if less exciting) to just do the old cvs add+rm thing, and make the first
>> commit log in the new location "renamed from foo".
>
> But then we lose the log.
Not really -- it's still there in the old deleted file. My practice is
simply to put in a pointer to the old file as the first commit message
in the new file, so that someone interested in pre-rename history can
look there, e.g.:
cvs add foo; cvs commit -m"Renamed from bar" foo
Alternatively, you can do as David suggested and simply use the entire
old log as the initial commit message.
Personally I don't think it's worth the bother -- CVS logs are handy on
occasion, but they're not _that_ commonly used; if somebody has to
expend a slight bit of extra effort to look at old logs (e.g., follow
the pointer to the old name), it's not a tragedy. What's most important
is that the information _is_ still there.
Furthermore, as Stefan pointed out, CVS logs are typically not as
necessary in GNU projects because the info is usually already there in
the ChangeLogs (often in a more useful form).
>> The reason it's bad, as I understand it, is that it essentially changes
>> history; I'm not entirely sure of the all the user-visible repercussions, but
>> I'm not sure I want to find out the hard way...
>
> Hm... I don't quite follow you. The CVS tree is (almost) just a
> bunch of ,v files.
The problem is that you're changing history: By renaming the ,v file,
in effective you retroactively rename the file in old versions too. So
sombody that tries to check out an old version using a tag (or -D...)
will see the old version _with the more recent renames applied_.
This loses for a few reasons: old Makefiles won't work correctly, diffs
between these "retroactively updated" old versions and newer (post
rename) versions won't actually reflect the "real" difference, possibly
causing great confusion in merging, etc.
It may be that in practice the bad effects are "acceptable" -- maybe
nobody at all cares about old versions -- but it's really hard to tell
in advance, and if it turns out later there _is_ a problem, well, then
what?
It's all around safer to use the boring and clunky rm+add method. It is
less likely to yield surprises, and I think where source control is
concerned, surprises are usually not what you want ... :-)
[From my arch-gateway perspective, I presume that if you do the rename
on both the v5-10 branch and the trunk simultaneously, the user-visible
effect (from "cvs update") will be the same: the old names will
disappear and will seem to be added under the new names.
But ... I don't really know, and thus and somewhat worried.]
-Miles
--
We are all lying in the gutter, but some of us are looking at the stars.
-Oscar Wilde
next prev parent reply other threads:[~2004-10-21 1:28 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 19:26 Moving files from lisp/gnus/ to lisp/net/? Simon Josefsson
2004-10-15 19:37 ` Simon Josefsson
2004-10-15 23:27 ` Miles Bader
2004-10-16 2:08 ` Ted Zlatanov
2004-10-16 13:52 ` Richard Stallman
2004-10-17 13:45 ` Simon Josefsson
2004-10-18 13:58 ` Richard Stallman
2004-10-24 12:24 ` Simon Josefsson
2004-10-25 13:13 ` Richard Stallman
2004-10-25 14:13 ` Simon Josefsson
2004-10-27 10:47 ` Richard Stallman
2004-10-27 19:08 ` Simon Josefsson
2004-10-29 4:32 ` Richard Stallman
2004-10-29 21:25 ` Simon Josefsson
2004-11-01 20:09 ` Ted Zlatanov
2004-11-01 20:31 ` Simon Josefsson
2004-11-02 18:30 ` Ted Zlatanov
2004-11-02 21:15 ` Stefan Monnier
2007-11-02 15:02 ` Richard Stallman
2007-11-05 10:16 ` Simon Josefsson
2007-11-06 8:38 ` Richard Stallman
2007-11-06 14:01 ` Daiki Ueno
2007-11-07 7:55 ` Richard Stallman
2007-11-08 0:46 ` Daiki Ueno
2007-11-08 17:40 ` Richard Stallman
[not found] ` <54a15d860711081633k364caf30r3b75464be8a060fa@mail.gmail.com>
2007-11-09 13:40 ` Fwd: " Daiki Ueno
[not found] ` <E1IqbtM-0003DR-P8@fencepost.gnu.org>
2007-11-10 4:53 ` Daiki Ueno
2007-11-10 7:07 ` Daiki Ueno
2007-11-10 20:03 ` Stefan Monnier
2007-11-11 0:04 ` Daiki Ueno
2007-11-11 19:33 ` Richard Stallman
2007-11-12 8:54 ` Daiki Ueno
2007-11-13 5:10 ` Richard Stallman
2007-11-14 3:45 ` Daiki Ueno
2007-11-14 5:44 ` Michael Albinus
2007-11-14 14:54 ` Stefan Monnier
2007-11-14 15:13 ` Michael Albinus
2007-11-14 17:30 ` Stefan Monnier
2007-11-15 3:08 ` Richard Stallman
2007-11-15 3:47 ` Stefan Monnier
2007-11-16 4:28 ` Richard Stallman
2007-11-15 0:23 ` Miles Bader
2007-11-15 3:08 ` Richard Stallman
2007-11-11 5:22 ` Richard Stallman
2007-11-10 19:53 ` Tom Tromey
2004-10-15 20:05 ` Miles Bader
2004-10-15 21:15 ` Simon Josefsson
2004-10-16 7:43 ` Thien-Thi Nguyen
2004-10-16 13:44 ` Miles Bader
2004-10-15 20:44 ` Stefan Monnier
2004-10-15 21:06 ` Simon Josefsson
2004-10-15 21:32 ` Lars Magne Ingebrigtsen
2004-10-15 21:47 ` Simon Josefsson
2004-10-15 21:52 ` Stefan Monnier
2004-10-18 1:04 ` Miles Bader
2004-10-18 13:59 ` Richard Stallman
2004-10-20 10:27 ` Lars Magne Ingebrigtsen
2004-10-20 10:50 ` Miles Bader
2004-10-20 11:22 ` Ralf Angeli
2004-10-20 11:39 ` Ralf Angeli
2004-10-21 1:09 ` Miles Bader
2004-10-20 11:32 ` Lars Magne Ingebrigtsen
2004-10-20 11:56 ` Karl Fogel
2004-10-20 12:38 ` David Kastrup
2004-10-20 13:06 ` Stefan Monnier
2004-10-20 12:34 ` David Kastrup
2004-10-21 1:28 ` Miles Bader [this message]
2004-10-21 5:03 ` Lars Magne Ingebrigtsen
2004-10-21 5:49 ` Miles Bader
2004-10-21 10:05 ` Kim F. Storm
2004-10-23 7:48 ` Lars Magne Ingebrigtsen
2004-10-25 1:02 ` Miles Bader
2004-10-25 10:14 ` Simon Josefsson
2004-10-25 17:46 ` Lars Magne Ingebrigtsen
2004-10-25 22:41 ` Miles Bader
2004-10-27 17:21 ` Lars Magne Ingebrigtsen
2004-10-28 2:21 ` Miles Bader
2004-10-26 7:28 ` Kai Grossjohann
2004-10-27 17:21 ` Lars Magne Ingebrigtsen
2004-10-16 13:52 ` Richard Stallman
2004-10-18 17:54 ` Ted Zlatanov
2004-10-18 21:36 ` Reiner Steib
2004-10-21 18:45 ` Ted Zlatanov
2004-10-22 0:25 ` Miles Bader
2004-10-24 12:13 ` Simon Josefsson
2004-10-24 12:20 ` Miles Bader
2004-10-24 13:41 ` Simon Josefsson
2004-10-24 22:18 ` Stefan
2004-10-25 10:08 ` Simon Josefsson
2004-10-25 11:55 ` Stefan
2004-10-25 13:07 ` Simon Josefsson
2004-10-26 9:05 ` Richard Stallman
2004-10-26 9:26 ` Simon Josefsson
2004-10-19 16:45 ` Richard Stallman
2004-10-21 18:45 ` Ted Zlatanov
2004-10-23 4:49 ` Richard Stallman
2004-10-24 12:59 ` Simon Josefsson
2004-10-24 13:05 ` Move sha1.el and hex-util.el from lisp/gnus/ to lisp/net/ (was: Re: Moving files from lisp/gnus/ to lisp/net/?) Simon Josefsson
2004-10-25 13:13 ` Richard Stallman
2004-10-25 14:23 ` Move sha1.el and hex-util.el from lisp/gnus/ to lisp/net/ Simon Josefsson
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=buopt3cq2p7.fsf@mctpc71.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--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.