unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 26238@debbugs.gnu.org
Subject: bug#26238: core-updates: Fix time zone bug in `date` 8.26
Date: Mon, 27 Mar 2017 11:35:58 -0400	[thread overview]
Message-ID: <20170327153558.GA4480@jasmine> (raw)
In-Reply-To: <87fuhzkl33.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

On Mon, Mar 27, 2017 at 01:36:32PM +0200, Ludovic Courtès wrote:
> Marius Bakke <mbakke@fastmail.com> skribis:
> 
> > Leo Famulari <leo@famulari.name> writes:
> >
> >> On Sun, Mar 26, 2017 at 10:29:38PM +0200, Marius Bakke wrote:
> >>> I don't object to the graft, as it does sound like a serious regression.
> >>> My reaction was mostly a "flight" response after seeing the gnulib patch
> >>> that this depends upon (the parse_datetime2 API change).
> >>> 
> >>> https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4e6e16b3f43ce96302b1e52e48730c1f15e18c14
> >>> 
> >>> Are you working on backporting it?
> >>
> >> Ah, I failed to understand that it would be required to backport the
> >> gnulib commit as well. That does look hairy.
> >
> > Maybe grafting 8.27 is better. It would be good to build it out on a new
> > core-updates branch quickly to catch any problems it might introduce.
> 
> Let’s merge this one first.  :-)

Yeah, and I think we'll have to skip this bug fix for now,
unfortunately. Unless somebody else feels up to the task of backporting
the gnulib changes.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-03-27 15:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170324162234.GA32596@jasmine>
     [not found] ` <87d1d4p1nr.fsf@gnu.org>
     [not found]   ` <20170326200114.GA9140@jasmine>
2017-03-27  8:27     ` bug#26238: core-updates: Fix time zone bug in `date` 8.26 Ludovic Courtès
2017-04-17 21:30       ` Ludovic Courtès
2017-04-17 21:37         ` Marius Bakke
2017-04-18  7:54           ` Ludovic Courtès
2017-04-18 18:37             ` Marius Bakke
2017-04-18 21:34               ` Ludovic Courtès
2017-04-19 16:49                 ` Marius Bakke
2017-04-19 20:00                   ` Ludovic Courtès
2017-04-19 20:12                     ` Marius Bakke
     [not found] ` <87r31kwn7e.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
     [not found]   ` <20170326201300.GA9812@jasmine>
     [not found]     ` <87k27bwzm5.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
     [not found]       ` <20170326205552.GA3104@jasmine>
     [not found]         ` <87h92fwwza.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
2017-03-27 11:36           ` Ludovic Courtès
2017-03-27 15:35             ` Leo Famulari [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=20170327153558.GA4480@jasmine \
    --to=leo@famulari.name \
    --cc=26238@debbugs.gnu.org \
    --cc=ludo@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).