From: Yngve Svendsen <yngve.svendsen@sun.com>
To: "Andrew J. Gray" <andrewg@gnu.org>, hatzis@juniper.net
Cc: help-gnats@gnu.org
Subject: Re: patch to display new PR number for new submissions
Date: Tue, 29 Apr 2003 20:24:00 -0000 [thread overview]
Message-ID: <5.2.1.1.0.20030429221626.00d43ba8@ms-etro01-01.norway.sun.com> (raw)
In-Reply-To: <200302090649.h196nS607794@localhost.localdomain>
At 17:49 09.02.2003 +1100, Andrew J. Gray wrote:
>OK, I will hold this patch for when we create a 4.1 branch.
I would like to suggest that we branch for a 4.0 release now. I think
quality is good enough for a 4.0 release, and any remaining changes to 4.0
should be only very minor bugfixes that should merge easily into the head
branch.
- Yngve
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2003-04-29 20:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 15:08 GNU GNATS 4.0 beta2 released Andrew J. Gray
2002-12-02 15:11 ` compiling gnats 4.0 beta 2 Steve Friedman
2002-12-04 2:36 ` Andrew J. Gray
2002-12-03 19:52 ` patch to display new PR number for new submissions Mel Hatzis
2002-12-04 3:02 ` Andrew J. Gray
2002-12-08 7:58 ` Andrew J. Gray
2002-12-08 12:27 ` Yngve Svendsen
2002-12-08 23:11 ` Patching the manual Lars Henriksen
2002-12-12 3:58 ` Yngve Svendsen
2002-12-12 6:29 ` patch to display new PR number for new submissions Andrew J. Gray
2002-12-08 23:11 ` Mel Hatzis
2003-02-02 9:32 ` Andrew J. Gray
2003-02-03 20:46 ` Mel Hatzis
2003-02-03 20:51 ` Yngve Svendsen
2003-02-03 21:17 ` Mel Hatzis
2003-02-03 22:10 ` Yngve Svendsen
2003-02-09 8:28 ` Andrew J. Gray
2003-02-09 7:48 ` Andrew J. Gray
2003-04-29 20:24 ` Yngve Svendsen [this message]
2002-12-09 10:54 ` dirk bergstrom
2002-12-14 14:26 ` Andrew J. Gray
2003-08-30 11:58 ` Andrew J. Gray
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=5.2.1.1.0.20030429221626.00d43ba8@ms-etro01-01.norway.sun.com \
--to=yngve.svendsen@sun.com \
--cc=andrewg@gnu.org \
--cc=hatzis@juniper.net \
--cc=help-gnats@gnu.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).