Re: [Queue-developers] patches: rlimits-bug-fix, queued--foreground

[W. G. K. <wer...@ya...>]

Quoting QingLong <qin...@Bo...>:

> >
> > Obviously, there are a number of patches, so it would be good
> > if someone would  look through all of these and iron out any conflicts.
> >
>    I can try if you let me.
>  I do have some experience with CVS.
>  But I am afraid I'll not be able to test all the changes introduced
>  by the patches waiting to be applied against a wide variety of system
>  platforms. I only have Linux (I also have openbsd, ultrix, tru64 and irix6,
>  but they aren't worth even trying on due to awfull development environment).

That's OK. If you patch the CVS repository in a reasonable way (i.e., it
compiles and runs on Linux) others will test the code for other systems once you

announce the changes. The point of CVS is that it lowers the barriers to getting

the latest, patched source, so many more "eyeballs" can test each new version
and find the bugs on their platforms, thus accelerating bugfixes and overall
development.

> > Obviously, if you are uncomfortable with the CVS archive,
> >
>    Although I am not very comfortable with CVS
>  (that's due to CVS disabilities), I can stay with it.
>
> >
> > Let me know what your Sourceforge username is (sourceforge is at
> > http://www.gnuqueue.org) and I'll enable you for write access to the CVS
> > repository so that you can apply your patches.
> >
>    Ok, finally I've managed to reach it via https and register myself.
>  My Sourceforge username is QingLong (surprised? :).
>
>       QingLong.

Ok, I've listed you as a sourceforge developer, with write access to the CVS
archives. (You also have some permissions over the patch manager should you care

to exercise this to mark patches you merged into the repository as "closed.")

Contrary to your previous posting, this is a very select group! The others are
all programmers who requested write access via the FSF (some at the request of
RMS) or long-time Queue developers who were grand-fathered in.

Note that, it seems my registration services DNS server is down right now, so
the URL (temporarily) is http://queue.sourceforge.net rather than
http://www.gnuqueue.org . (This must be affecting a lot of sites.)

So, to access CVS, you have to have ssh1 (secure shell version 1, get it from
http://www.ssh.com . The source is free for Unix systems.)

For developers with write-access:

You do a "setenv CVS_RSH ssh1" to the path of ssh1 or whatever is appropriate
for your system.

"cvs -z3 -d:pserver:ano...@cv...:/cvsroot/queue co
queue-development"

Enter your SourceForge password when prompted for a password. (You can get rid
of the constant need to enter your password by pasting an ssh certificate into a

form at Sourceforge. But, this is for advanced ssh users.)

Make changes to the source in queue-development, including logging them in
"ChangeLog".

When you are read to commit, just type "cvs ci" from the queue-development
directory, make a brief log entry into the editor it brings up, save, enter
password. Then post a message to queue-developers saying there is a new release
on CVS, and then can download it by just running "cvs update" from their GNU
Queue directory.

Complete CVS docs are on http://sourceforge.net/cvs/?group_idV05

----- End forwarded message -----