From: Warren Young <warren@etr-usa.com>
To: cygwin-apps@cygwin.com
Subject: Re: upload protocol
Date: Wed, 10 Oct 2012 09:31:00 -0000 [thread overview]
Message-ID: <50754087.5020600@etr-usa.com> (raw)
In-Reply-To: <20121009165836.GA11886@ednor.casa.cgf.cx>
On 10/9/2012 10:58 AM, Christopher Faylor wrote:
> Would it make sense to always wait for an "RFU" after an "ITP"?
That's how I thought it always worked. To my mind, ITP is only a trial
run, asking experienced packagers to test that everything's okay. RFU
is exactly what it says: the request for upload. ITP followed by GTG
implies that an RFU is coming shortly, but I agree with Chris, nothing
should happen until that RFU *does* come. It gives the packager a
chance to change something minor brought up in the ITP discussion, for
example.
As it happens, I think this sort of gun-jumping happened with the
Doxygen 1.8.0-1 packages. I gave a GTG with reservations to the ITP,
several days ago. David said in the thread he was off working on
addressing some of those reservations, but then yesterday Corinna
uploaded from the ITP message.
I'm not regretting my GTG. I thought the packages were at least no
worse than my 1.7.4-1 packages that David's packages replace. But, I
think David was expecting a second chance before sending the RFU.
next prev parent reply other threads:[~2012-10-10 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 16:58 Christopher Faylor
2012-10-09 18:30 ` upload protocol (Use of GTG?) Jari Aalto
2012-10-09 18:55 ` Christopher Faylor
2012-10-09 19:50 ` upload protocol marco atzeri
2012-10-10 9:06 ` Corinna Vinschen
2012-10-10 9:31 ` Warren Young [this message]
2012-10-10 14:01 ` Christopher Faylor
2012-10-10 17:47 ` David Stacey
2012-10-10 19:35 ` Warren Young
2012-10-11 9:54 ` Corinna Vinschen
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=50754087.5020600@etr-usa.com \
--to=warren@etr-usa.com \
--cc=cygwin-apps@cygwin.com \
/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).