cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Ken Barozzi" <baro...@nicolaken.com>
Subject DO NOT REPLY [PATCH QUEUE] Summary 16-01-2002
Date Wed, 16 Jan 2002 07:44:36 GMT
-----------------------------------------------------------
          Please do not reply to this mail.
-----------------------------------------------------------

***********************************************************
             __   __   __   __   __   __
            (___ (__) (___ (__) (__) |  )

           __   __  _|_   __  |__   ___    __
          |__) (__(  |_, (___ |  ) (__/_ __)
          |
***********************************************************
*****************  patches in queue: 2 ********************
***********************************************************

-----------------------------------------------------------
[PATCH] Form encoding enhancement.
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5593

DATE:       26/12/2001 
AUTHOR(S):  miyabe@jzf.co.jp (MIYABE Tatsuhiko)
REVIEWER:   nobody
APPLIES TO: HEAD.

-----------------------------------------------------------
[PATCH] New Interactive build target
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5871

DATE:       15/01/2002 
AUTHOR(S):  xml-cocoon@nicolaken.com (Nicola Ken Barozzi)
REVIEWER:   nobody
APPLIES TO: HEAD.

*************************that's it!************************

------------------------patch HOWTO------------------------

Send patches to http://nagoya.apache.org/bugzilla/
specifying [PATCH] in the summary.
Bugzilla sends a mail automatically to this list.
Reviewers will mark it FIXED there when applied.
Patches not sent to Bugzilla will not be reviewed.
-----------------------------------------------------------
This file is updated regularly at least once a week.
If you don't find the patch you submitted to bugzilla
after one week, please notify xml-cocoon@nicolaken.com
-----------------------------------------------------------
There is usually a HEAD branch and a previous-version
branch that are maintained. Where will the patch go?
1. If it is a bug fix it should go to both branches
2. If something is totally new it goes into HEAD scratchpad.
3. Something in between, but does not break backward
   compatibility _may_ go into both (and may not)
4. For everything else, a vote is required  so
   first it may go into HEAD, and then be VOTEd in order
   to sync this into branch.
Please note that structural changes have to be VOTEd first.
--------------------------------------------------------EOF


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message