unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org, Sed Devel <sed-devel@gnu.org>
Subject: Re: new snapshot available: sed-4.7.13-3c1e
Date: Wed, 8 Jan 2020 12:27:31 -0800	[thread overview]
Message-ID: <CA+8g5KHh4JNWp1MaBFq8k-+pnL2uMoxARBOUkcFeOXoGOaZgtA@mail.gmail.com> (raw)
In-Reply-To: <878smitgrb.fsf@gnu.org>

On Wed, Jan 8, 2020 at 10:59 AM Jan Nieuwenhuizen <janneke@gnu.org> wrote:
>
> Jim Meyering writes:
>
> > On Mon, Jan 6, 2020 at 10:08 AM Jan Nieuwenhuizen <janneke@gnu.org> wrote:
> >>
> >> Jim Meyering writes:
> >>
> >> > It's been a year since the preceding release, so this feels overdue.
> >> > Please give it a whirl and let us know how it goes.
> >>
> >> Builds fine on GNU Guix master.  Log attached.
> >
> > Thanks for testing/reporting.
>
> You're welcome.  Thinking about this, it only makes sense for essential
> core/bootstrap packages, especcialy GNU packages such as SED to check
> them on Guix before a release.  This was kind of a coincidence and
> personal interest; I am wondering if it would make sense to do this
> more structurally, and add make, awk, coreutils, ... for example.

If you want to test diffutils, gzip and grep prereleases, I won't complain.
Most of us announce prereleases to platform-testers@gnu.org .

> >> Would you be willing to also provide a GZIP compressed version of future
> >> sed releases too?
> >
> > Done via the attached.
>
> Beautiful, thank you.  By replying with a patch you make me realise that
> I could have helped by writing it for you when making the request.  Oh
> well.  I don't see it in git yet, is that right?

Just pushed.

      reply	other threads:[~2020-01-08 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+8g5KEAsnrMMOTFcy=8y+5KwriuBqiMk_MTj3ayan6sZO0mMg@mail.gmail.com>
2020-01-06 18:08 ` new snapshot available: sed-4.7.13-3c1e Jan Nieuwenhuizen
2020-01-08  5:38   ` Jim Meyering
2020-01-08  9:54     ` Jan Nieuwenhuizen
2020-01-08 20:27       ` Jim Meyering [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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=CA+8g5KHh4JNWp1MaBFq8k-+pnL2uMoxARBOUkcFeOXoGOaZgtA@mail.gmail.com \
    --to=jim@meyering.net \
    --cc=guix-devel@gnu.org \
    --cc=janneke@gnu.org \
    --cc=sed-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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