From: Adam Spiers <adam@spiers.net>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Completion system directories
Date: Wed, 3 May 2000 10:57:43 +0100 [thread overview]
Message-ID: <20000503105743.B14353@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <200005030914.LAA24343@beta.informatik.hu-berlin.de>; from wischnow@informatik.hu-berlin.de on Wed, May 03, 2000 at 11:14:42AM +0200
Sven Wischnowsky (wischnow@informatik.hu-berlin.de) wrote:
> And finally: what is the easiest way to make these changes in the CVS
> repository? Is there really no simpler way than using `cvs add' and
> `cvs remove'? If not: urgh.
Renaming/moving files around is one of CVS' weaknesses. If we had
direct access to the CVS repository we could just copy the RCS files
directly, and that would preserve history. (See the FAQ for details
of this procedure.) But we don't. So I guess we can either ask the
sourceforge guys nicely, or obtain a tarball of the whole repository,
and declare the tree closed for a bit while someone messes around with
the tarball, and resubmits it for upload.
> And that with the `cvs commit aborted: broken pipe' I get at every
> second commit-attempt :-(
Hmm, no excuse for that. You should submit a bug to sourceforge.
next prev parent reply other threads:[~2000-05-03 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-03 9:14 Sven Wischnowsky
2000-05-03 9:57 ` Adam Spiers [this message]
2000-05-03 10:52 ` Bart Schaefer
2000-05-03 10:30 ` Bart Schaefer
2000-05-03 11:03 ` Andrej Borsenkow
2000-05-03 11:10 ` Peter Stephenson
2000-05-03 11:24 ` Geoff Wing
2000-05-03 16:35 ` Bart Schaefer
2000-05-03 16:51 ` Peter Stephenson
2000-05-03 11:35 ` Oliver Kiddle
2000-05-03 16:23 ` CVS merge conflicts (Re: Completion system directories) Bart Schaefer
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=20000503105743.B14353@thelonious.new.ox.ac.uk \
--to=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.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).