zsh-workers
 help / color / mirror / code / Atom feed
* Re: PATCH: AIX dep.&doc fix; development guidelines
@ 2000-04-06  7:23 Sven Wischnowsky
  2000-04-06 16:23 ` Zefram
  0 siblings, 1 reply; 15+ messages in thread
From: Sven Wischnowsky @ 2000-04-06  7:23 UTC (permalink / raw)
  To: zsh-workers


Bart Schaefer wrote:

> On Apr 5,  5:52pm, Oliver Kiddle wrote:
> } Subject: PATCH: AIX dep.&doc fix; development guidelines
> } 
> } 1. Has there been a final solution on how we are supposed to create the
> } ChangeLog entries.
> 
> Peter wants each developer to create his own.  This causes some oddities
> e.g. when Sven and I were both patching today -- article number refs get
> out of order, and I had to restart my commit because Sven sneaked one in
> between my "cvs update" and finishing writing the log message.

Oh, sorry, I feared that and had waited some time, tried update a
couple of times and then...

> ...
> 
> But with e.g. my patch to Makefile.in, I mailed off the "cvs diff" output
> and then waited for the patch to come back to me before committing, so I
> could reference the article number in the commitlog.  It appears that Sven
> has been doing this too.

Yesss, most annoying... it means that I can't continue hacking on the
next thing before the mail comes back. So zsh interrupts my real work
more often and in smaller time slices.


Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


^ permalink raw reply	[flat|nested] 15+ messages in thread
* Re: PATCH: AIX dep.&doc fix; development guidelines
@ 2000-04-07  8:38 Sven Wischnowsky
  0 siblings, 0 replies; 15+ messages in thread
From: Sven Wischnowsky @ 2000-04-07  8:38 UTC (permalink / raw)
  To: zsh-workers


Bart Schaefer wrote:

> On Thu, 6 Apr 2000, Zefram wrote:
> 
> > I'd forgotten that that form would clash with old subversion numbers.
> > I'm going to skip ahead 100 numbers, therefore, to get past that clash.
> > I suggest that everyone else using this scheme start off at patch
> > "pws100" etc.
> 
> OK, I'm almost convinced to give in.  Can I make one request?
> 
> At the time an actual release is done, will the maintainer (hi, Peter)
> please do a sweep of the ChangeLog and convert all the "zefram1XX" etc.
> into the actual article numbers?

Placing the burden on Peter again... Hm, that's not as kind as I would 
like to be. And searching all those numbers is a rather tedious job.

I'm torn in two, especially because I find the (real) message numbers
rather convenient myself.

And I've just finished my emacs-lisp support for all this stuff...

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


^ permalink raw reply	[flat|nested] 15+ messages in thread
* PATCH: AIX dep.&doc fix; development guidelines
@ 2000-04-05 16:52 Oliver Kiddle
  2000-04-05 18:06 ` Bart Schaefer
  0 siblings, 1 reply; 15+ messages in thread
From: Oliver Kiddle @ 2000-04-05 16:52 UTC (permalink / raw)
  To: Zsh workers

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


^ permalink raw reply	[flat|nested] 15+ messages in thread

end of thread, other threads:[~2000-04-08 22:10 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-04-06  7:23 PATCH: AIX dep.&doc fix; development guidelines 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
  -- strict thread matches above, loose matches on Subject: below --
2000-04-07  8:38 Sven Wischnowsky
2000-04-05 16:52 Oliver Kiddle
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

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