From: Jari Aalto <jari.aalto@cante.net>
To: cygwin-apps@cygwin.com
Subject: Re: upload protocol (Use of GTG?)
Date: Tue, 09 Oct 2012 18:30:00 -0000 [thread overview]
Message-ID: <87sj9ncxbt.fsf@picasso.cante.net> (raw)
In-Reply-To: <20121009165836.GA11886@ednor.casa.cgf.cx> (Christopher Faylor's message of "Tue, 9 Oct 2012 12:58:36 -0400")
On 2012-10-09 12:58, 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.
Perhaps appending "GTG" to a end of subject would be all that is
needed to mark the thread finished.
Jari
next prev parent reply other threads:[~2012-10-09 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 16:58 upload protocol Christopher Faylor
2012-10-09 18:30 ` Jari Aalto [this message]
2012-10-09 18:55 ` upload protocol (Use of GTG?) 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
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=87sj9ncxbt.fsf@picasso.cante.net \
--to=jari.aalto@cante.net \
--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).