From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "ZSH Workers Mailing List" <zsh-workers@sunsite.dk>
Subject: Re: What about this? (was: RE: Zsh broken after the latest build patches)
Date: Mon, 23 Apr 2001 16:24:57 +0000 [thread overview]
Message-ID: <1010423162458.ZM14874@candle.brasslantern.com> (raw)
In-Reply-To: <000701c0cbb1$4662bda0$21c9ca95@mow.siemens.ru>
On Apr 23, 8:53am, Andrej Borsenkow wrote:
} Subject: What about this? (was: RE: Zsh broken after the latest build patc
}
} > I backed out the following and now zsh works again.
} >
} > 2001-04-19 Clint Adams <schizo@debian.org>
}
} I meant, in my local version, not in CVS of course. The problem is, I
} currently cannot even update cvs ...
I agree that we should either back this out entirely, or branch for
the 4.0.1 release and back it out on the branch.
Andrej, is is possible to back those patches out simply by returning to
an earlier CVS revision of the files, or have some of the other termcap
or terminfo config changes gotten mised in so the shared linking changes
have to be backed out separately? If returning to an earlier revision
is sufficient, we can simply create the branch off those revisions, else
we'll have to branch from the current state and then back them out.
If the consensus is to branch, the recommended procedure is to first tag
(without -b) the pre-branch revisions as the "branch point" and then do
the actual branch tag (with -b). This makes it easier to identify the
common ancestor should code have to be merged onto or from the branch.
I can deal with this if necessary.
--
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-04-23 16:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-21 8:37 Zsh broken after the latest build patches Andrej Borsenkow
2001-04-21 10:51 ` Andrej Borsenkow
2001-04-23 4:53 ` What about this? (was: RE: Zsh broken after the latest build patches) Andrej Borsenkow
2001-04-23 16:24 ` Bart Schaefer [this message]
2001-04-23 16:44 ` Peter Stephenson
2001-04-23 17:41 ` Bart Schaefer
2001-04-23 17:58 ` Peter Stephenson
2001-04-23 23:08 ` PATCH: " Clint Adams
2001-04-23 18:00 ` Andrej Borsenkow
2001-04-23 18:22 ` Bart Schaefer
2001-04-23 19:44 ` PATCH: revert Clint's build patches Andrej Borsenkow
2001-04-24 6:40 ` Bart Schaefer
2001-04-24 8:50 ` Andrej Borsenkow
2001-04-24 5:33 ` PATCH: The last, I really hope, subscripting tweak for a long while 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=1010423162458.ZM14874@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).