From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: <zsh-workers@sunsite.dk>
Subject: Re: Moving Functions
Date: Wed, 14 Mar 2001 08:40:46 +0000 [thread overview]
Message-ID: <1010314084046.ZM951@candle.brasslantern.com> (raw)
In-Reply-To: <001c01c0ac5f$d052ece0$21c9ca95@mow.siemens.ru>
On Mar 14, 11:21am, Andrej Borsenkow wrote:
}
} cvs add/remove has a problem of not preserving revision history
}
} Alternative way is to directly modify repository
I don't think we have direct access to the repository, so add/remove is
all we can do.
The convention is to put the name of the new file in each removed file's
commit log, and vice-versa. That means a whole lot of individual commits
rather than one big one, though.
It might also be a good idea to "cvs tag" everything before doing any of
this. I know Peter has tagged the prereleases, but there have been some
intervening commits.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-03-14 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-14 8:12 Sven Wischnowsky
2001-03-14 8:17 ` Ollivier Robert
2001-03-14 8:21 ` Andrej Borsenkow
2001-03-14 8:40 ` Bart Schaefer [this message]
2001-03-14 11:32 ` Peter Stephenson
2001-04-02 10:59 Moving functions Sven Wischnowsky
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=1010314084046.ZM951@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).