From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: upload protocol
Date: Tue, 09 Oct 2012 19:50:00 -0000 [thread overview]
Message-ID: <50747FFB.4030009@gmail.com> (raw)
In-Reply-To: <20121009165836.GA11886@ednor.casa.cgf.cx>
On 10/9/2012 6:58 PM, Christopher Faylor wrote:
> Would it make sense to always wait for an "RFU" after an "ITP"?
> As an uploader, I'd rather not have to scan conversations for clues
> for when a package is ready for upload.
>
> I was actually waiting for Jari to send an RFU for the packages that
> he'd recently ITP'ed but, now that I think of it, maybe that's not
> what we usually do.
>
> I'd like to propose that we always require an RFU.
>
> cgf
>
fine for me
Marco
next prev parent reply other threads:[~2012-10-09 19:50 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 ` marco atzeri [this message]
2012-10-10 9:06 ` upload protocol Corinna Vinschen
2012-10-10 9:31 ` Warren Young
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=50747FFB.4030009@gmail.com \
--to=marco.atzeri@gmail.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).