Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Completion system directories

X-seq: zsh-workers 11098
From: Adam Spiers <adam@xxxxxxxxxx>
To: zsh-workers@xxxxxxxxxxxxxx
Subject: Re: Completion system directories
Date: Wed, 3 May 2000 10:57:43 +0100
In-reply-to: <200005030914.LAA24343@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>; from wischnow@xxxxxxxxxxxxxxxxxxxxxxx on Wed, May 03, 2000 at 11:14:42AM +0200
Mail-followup-to: zsh-workers@xxxxxxxxxxxxxx
Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
References: <200005030914.LAA24343@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: Adam Spiers <adam@xxxxxxxxxx>

Sven Wischnowsky (wischnow@xxxxxxxxxxxxxxxxxxxxxxx) 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.

Follow-Ups:
- Re: Completion system directories
  - From: Bart Schaefer

References:
- Completion system directories
  - From: Sven Wischnowsky

Messages sorted by: Reverse Date, Date, Thread, Author