GNU bug report logs - #22070
Recreating release 1.6 from git

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Jim Meyering <jim <at> meyering.net>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#22070: closed (Recreating release 1.6 from git)
Date: Wed, 16 Mar 2016 01:57:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 15 Mar 2016 18:55:46 -0700
with message-id <CA+8g5KHU80eTkgZLKRxbkLNs9Ysbk29ejg324ciSktb4C=+7Sg <at> mail.gmail.com>
and subject line Re: bug#22070: Recreating release 1.6 from git
has caused the debbugs.gnu.org bug report #22070,
regarding Recreating release 1.6 from git
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
22070: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22070
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Doug Evans <dje <at> google.com>
To: bug-gzip <at> gnu.org
Subject: Recreating release 1.6 from git
Date: Tue, 1 Dec 2015 10:09:37 -0800

Hi.

Is there a recipe for recreating (as close as possible, but not
necessarily identical to) the 1.6 release from git?

There is a v1.6 tag so I can begin with that.
It's the next step I'm not clear on.
I can run the bootstrap script and get something that's buildable,
but I'm left with, IIUC, all of gnulib instead of just the pieces that
went into the 1.6 release.

There's also the issue of using the same autoconf/automake/etc. but I
can manage that as needed.

TIA

[Message part 3 (message/rfc822, inline)]

From: Jim Meyering <jim <at> meyering.net>
To: 22070-done <at> debbugs.gnu.org
Subject: Re: bug#22070: Recreating release 1.6 from git
Date: Tue, 15 Mar 2016 18:55:46 -0700

tags 22070 notabug
done

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.