From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: Re: 4.0.1 - arguments test fails
Date: Wed, 6 Jun 2001 12:51:29 +0200 (MET DST) [thread overview]
Message-ID: <200106061051.MAA23925@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <Tc0a88d0153f9cb6e12@mailsweeper01.cambridgesiliconradio.com>
Peter Stephenson wrote:
> Sven Wischnowsky wrote:
> > I'm going to commit this now, do I have to commit it somewhere else, too
> > (because of branching or something)?
>
> Yes, you have to
> cvs -d '<the-sourceforge-stuff>' checkout -r zsh-4_0-patches zsh
> and apply it.
Aha. I have that now, but whenever I try to commit the applied patches
there, it says:
cvs commit: Examining ...
...
cvs [server aborted]: "commit" requires write access to the repository
What am I doing wrong?
> In general they shouldn't go straight onto the 4.0 branch until after a bit
> of testing, but this one is presumably an improvement. Bart's suggestion
> is someone (probably me, it looks like) applies all the 4.0 changes, but
> I'm not enthusiastic about doing it all myself at the moment.
Bart's 14744 would be fine with me (when I've learned how to commit there...).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev parent reply other threads:[~2001-06-06 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-01 22:28 Andrej Borsenkow
2001-06-02 0:04 ` Peter Stephenson
2001-06-02 1:07 ` Bart Schaefer
2001-06-02 3:52 ` Bart Schaefer
2001-06-06 9:21 ` PATCH: " Sven Wischnowsky
2001-06-06 9:51 ` Peter Stephenson
2001-06-06 10:18 ` Branch patches (Re: PATCH: Re: 4.0.1 - arguments test fails) Bart Schaefer
2001-06-06 10:51 ` Sven Wischnowsky [this message]
2001-06-06 10:58 ` PATCH: Re: 4.0.1 - arguments test fails Bart Schaefer
2001-06-06 11:06 ` Sven Wischnowsky
2001-06-06 11:00 ` Andrej Borsenkow
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=200106061051.MAA23925@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).