public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: Richard Biener <richard.guenther@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [patch] build xz (instead of bz2) compressed tarballs and diffs
Date: Wed, 24 May 2017 19:21:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.21.1705242104360.3529@anthias.pfeifer.com> (raw)
In-Reply-To: <4ba45957-1500-13e0-4784-a038e7d3034c@ubuntu.com>

On Tue, 23 May 2017, Matthias Klose wrote:
> Looks like the copy of the script on gcc.gnu.org affects all active branches.

Yeah, I just run into this myself (and scratched my had until I
debugged this, admittedly quickly).

> the May 23 GCC 5 snapshot was created successfully.  Is this acceptable? 

Well, I guess it's a done deed.  Probably a good idea to send a note
to gcc@gcc.gnu.org at least; I added the one below to our main page.

Gerald

Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.1053
diff -u -r1.1053 index.html
--- index.html	9 May 2017 07:20:38 -0000	1.1053
+++ index.html	24 May 2017 19:08:02 -0000
@@ -46,6 +46,10 @@
 <h2 id="news">News</h2>
 <dl>
 
+<dt><span>Weekly snapshots now use xz compression</span>
+    <span class="date">[2017-05-24]</span></dt>
+    <dd>...instead of bzip2.</dd>
+
 <dt><span><a href="gcc-7/">GCC 7.1</a> released</span>
     <span class="date">[2017-05-02]</span></dt>
     <dd></dd>

      parent reply	other threads:[~2017-05-24 19:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15  1:35 Matthias Klose
2017-05-15 14:11 ` Joseph Myers
2017-05-15 14:15   ` Markus Trippelsdorf
2017-05-15 18:38     ` Jakub Jelinek
2017-05-15 19:13       ` Markus Trippelsdorf
2017-05-23 23:22         ` Matthias Klose
2017-05-18 10:41 ` Richard Biener
2017-05-23 23:56   ` Matthias Klose
2017-05-24  7:23     ` Richard Biener
2017-05-24 19:21     ` Gerald Pfeifer [this message]

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=alpine.LSU.2.21.1705242104360.3529@anthias.pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.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).