From: Oliver Kiddle <opk@u.genie.co.uk>
To: Zsh workers <zsh-workers@sunsite.auc.dk>
Subject: PATCH: AIX dep.&doc fix; development guidelines
Date: Wed, 05 Apr 2000 17:52:07 +0100 [thread overview]
Message-ID: <38EB6F37.A658A22A@u.genie.co.uk> (raw)
The patch fixes the latest AIX dependency problem and fixes a minor
error in the docs. I haven't commited it to cvs (sorry Peter) because I
haven't got ssh and cvs in the same place yet.
It would be nice to have the zsh-development-guide updated to reflect
the new guidelines now that we have CVS. Also, I'm not entirely clear
myself on what these new guidelines are:
1. Has there been a final solution on how we are supposed to create the
ChangeLog entries. It'd be nice to have a solution that doesn't depend
on using emacs (I'm more than happy to learn cvs but don't have the
time, inclination or disc space to learn emacs). Is the ChangeLog
modified just like any other file on the cvs server? If people can only
send a patch should they still include a patch for ChangeLog?
2. Should we still post patches for everything in addition to commiting
to cvs? For some things (like these AIX dependencies) it is hardly
worth it. With many changes the patches are useful, particularly when
they are just to functions and a recompile isn't necessary. It is also
useful that patches from people such as me can get sanity checked.
3. The .distfiles thing should be mentioned. I take it that we just add
and remove files from the list in it if we add and remove files?
Oliver Kiddle
--- Src/utils.c.bak Mon Apr 3 15:56:35 2000
+++ Src/utils.c Mon Apr 3 15:57:00 2000
@@ -2681,7 +2681,7 @@
}
/**/
-char *
+mod_export char *
nicedupstring(char const *s)
{
return nicedup(s, 1);
--- Doc/Zsh/compsys.yo.bak Wed Apr 5 17:16:57 2000
+++ Doc/Zsh/compsys.yo Wed Apr 5 17:18:18 2000
@@ -2794,7 +2794,7 @@
before executing the var(action) and hence may be used in it (normally
in an expansion like `tt($expl[@])').
-If the var(action) starts with `tt(= )' (a equal sign followed by a
+If the var(action) starts with `tt(= )' (an equals sign followed by a
space), tt(_arguments) will insert the contents of the var(argument)
field of the current context as the new first element in the tt(words)
special array and increments the value of the tt(CURRENT) special
next reply other threads:[~2000-04-05 16:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-05 16:52 Oliver Kiddle [this message]
2000-04-05 18:06 ` Bart Schaefer
2000-04-05 19:21 ` Peter Stephenson
2000-04-05 19:43 ` Peter Stephenson
2000-04-05 20:41 ` Bart Schaefer
2000-04-06 7:23 Sven Wischnowsky
2000-04-06 16:23 ` Zefram
2000-04-06 17:02 ` Bart Schaefer
2000-04-06 17:27 ` Zefram
2000-04-06 17:39 ` Bart Schaefer
2000-04-06 17:51 ` Zefram
2000-04-06 23:12 ` Bart Schaefer
2000-04-07 20:04 ` Peter Stephenson
2000-04-08 22:09 ` Bart Schaefer
2000-04-07 8:38 Sven Wischnowsky
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=38EB6F37.A658A22A@u.genie.co.uk \
--to=opk@u.genie.co.uk \
--cc=zsh-workers@sunsite.auc.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).