From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Major changes coming to procedure for uploading to sourceware (long)
Date: Thu, 17 Oct 2013 20:24:00 -0000 [thread overview]
Message-ID: <87iowv3au0.fsf@Rainer.invalid> (raw)
In-Reply-To: <20131017193321.GA2803@ednor.casa.cgf.cx> (Christopher Faylor's message of "Thu, 17 Oct 2013 15:33:21 -0400")
Christopher Faylor writes:
> No. This is for adding new/updated packages to the release. Putting
> old stuff in the staging area would certainly confuse things.
Thanks for the clarification.
>>My release area is non-empty but incomplete due to previous tests, but
>>I don't want to remove or add anything there unless I know how this
>>gets handled.
>
> I just wiped out and recreated your home directory. There are no old
> packages there now.
Confirmed, thank you.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2013-10-17 20:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 20:22 Christopher Faylor
2013-10-16 16:52 ` The upload system is live (Re: Major changes coming to procedure for uploading to sourceware) Christopher Faylor
2013-10-17 4:30 ` Christopher Faylor
2013-10-22 16:40 ` Chris Sutcliffe
2013-10-22 18:50 ` Christopher Faylor
2013-10-22 19:38 ` Achim Gratz
2013-10-22 19:59 ` Christopher Faylor
2013-10-22 20:18 ` Achim Gratz
2013-10-22 20:26 ` Christopher Faylor
2013-10-22 17:59 ` Andrew Schulman
2013-10-23 2:47 ` Yaakov (Cygwin/X)
2013-10-23 16:51 ` Reini Urban
2013-10-23 17:37 ` Christopher Faylor
2013-10-17 19:19 ` Major changes coming to procedure for uploading to sourceware (long) Achim Gratz
2013-10-17 19:33 ` Christopher Faylor
2013-10-17 20:24 ` Achim Gratz [this message]
2013-10-18 18:43 ` Achim Gratz
2013-10-18 19:00 ` Christopher Faylor
2013-10-18 20:39 ` Achim Gratz
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=87iowv3au0.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).