public inbox for
 help / color / mirror / Atom feed
From: Matthias Klose <>
To: Richard Biener <>
Cc: GCC Patches <>
Subject: Re: [patch] build xz (instead of bz2) compressed tarballs and diffs
Date: Tue, 23 May 2017 23:56:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 18.05.2017 03:34, Richard Biener wrote:
> On Mon, May 15, 2017 at 3:11 AM, Matthias Klose <> wrote:
>> As discussed on IRC with Jakub and Richard here are is a small patch which
>> builds xz compressed tarballs and diff files.
>> Tested with
>>   maintainer-scripts/gcc_release \
>>         -s snap:trunk -p <old bz2 tarball> diffs sources tarfiles
>>   maintainer-scripts/gcc_release \
>>         -s snap:trunk -p <old xz tarball> diffs sources tarfiles
>> and checked that the new tarball and diff files are compressed using xz.
>> Ok for the trunk and the gcc-7-branch?
> Ok.  The version on trunk can get the bz2 old-tar support removed after the next
> snapshot generation I  think.  Likewise the branch version after 7.2
> was released.

Looks like the copy of the script on affects all active branches.
the May 23 GCC 5 snapshot was created successfully.  Is this acceptable? If yes,
then the patch should probably go to the 5 and 6 branches as well.

Please copy the script again to enable the xz --best compression.


  reply	other threads:[~2017-05-23 23:22 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 [this message]
2017-05-24  7:23     ` Richard Biener
2017-05-24 19:21     ` Gerald Pfeifer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).