zsh-workers
 help / color / mirror / code / Atom feed
From: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
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 22:00:50 +0400 (MSD)	[thread overview]
Message-ID: <Pine.SV4.4.33.0104232156250.13064-100000@itsrm2.mow.siemens.ru> (raw)
In-Reply-To: <1010423162458.ZM14874@candle.brasslantern.com>

On Mon, 23 Apr 2001, Bart Schaefer wrote:

> 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.
>

It should (still) be possible to just reverse-apply four mentioned patches
(actually, there were three, and one unposted, but it was one line change.
Of course, unposted cvs commits make it harder to unapply them). At this
time patch applied cleanly with one line fuzz in termcap.mdd (I believe).
I actually meant, that I cannot just use cvs update currently because it
will reapply the patches again.

With everyone's consent I'll try to backout them again on up-to-date cvs
and commit it.

-andrej


  parent reply	other threads:[~2001-04-23 18:01 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
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 [this message]
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=Pine.SV4.4.33.0104232156250.13064-100000@itsrm2.mow.siemens.ru \
    --to=andrej.borsenkow@mow.siemens.ru \
    --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).