This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

"Please upload" email guidelines (was Re: Please upload: tzcode-2005r-1)


On Sun, Jan 08, 2006 at 04:54:06PM -0500, Christopher Faylor wrote:
>On Sun, Jan 08, 2006 at 03:15:32PM -0500, Christopher Faylor wrote:
>>Please, everyone, just keep these upload requests as short as possible.  It
>>reduces the possibility that someone (i.e., me) will miss something if the
>>only thing in the request is a bunch of URLs.
>
>Having just reread the above, and knowing how these things work, let me
>clarify.
>
>In these email messages, I would prefer to *just* see the URLs required
>to update a cywgin package.  Please do not include any other information
>in the request other than that, with the possible exception of a wget
>script for retrieving the packages.

Uh oh.  By "these email messages", I mean the "please upload" email
messages.  Other types of messages, like ITP or setup bug reports or
discussions about GBS can and should have all sorts of nice prose.

In fact, if someone wants to create a nice script for generating these
messages which incorporates wget to produce the desired directory
structure on sourceware for easy retrieval of new packages, that would
be great.

What I'd like is something that produces the package directory and any
required subdirectories.

So, a "please upload" could be nothing other than the shell script that
Volker sent in his OP.  Then a package uploader could cut and paste that
and run it on sourceware to retrieve the packages.  If every package
upload request had this type of thing it would reduce the possibility of
error when uploading.

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]