zsh-workers
 help / color / mirror / code / Atom feed
From: Paul Ackersviller <pda@sdf.lonestar.org>
To: zsh-workers@sunsite.dk
Subject: Updates to zsh-4_2-patches branch
Date: Tue, 27 Mar 2007 20:20:48 +0000	[thread overview]
Message-ID: <20070327202048.GA4134@sverige> (raw)

I promised to do this months ago, but didn't get far over the course
of the winter...  Excuses aside, I've been hard at it for the past
week or two, and have gotten up to about the middle of last year in
merging trunk changes onto the branch.  I started out a little too
agressively in trying to include everything possible, but quickly
dug myself into a hole.  Now that I have the basic strategy down,
I'd like to do some testing for a few days to ensure it all still
works before continuing onto the rest.

How comprehensive is the test suite, and are there any major gotchas?

One area I could use help or at least guidance on is files in Src/Zle/.
I've merged in only a few changes there, when it appeared to be
non-multibyte-related, but is it better to try leaving that completely
alone?  I fear a few multibyte changes that don't belong mat have crept
in, but I'll see how testing goes.

In terms of documenting what I've done, is there any value in sending
all the change numbers to this list?  There will be very many, so I'm
thinking those numbers would better go into the change comments for the
individual cvs revisions.


             reply	other threads:[~2007-03-28  0:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <pda@sdf.lonestar.org>
2007-03-27 20:20 ` Paul Ackersviller [this message]
2007-03-27 20:47   ` Peter Stephenson
2007-10-30  2:01   ` Geoff Wing
2007-11-02  4:03     ` Paul Ackersviller
2007-11-05  1:41       ` C03 test failure on " Paul Ackersviller

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=20070327202048.GA4134@sverige \
    --to=pda@sdf.lonestar.org \
    --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).