From: Alex Kost <alezost@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Timestamps in ...-autoloads.el files
Date: Sat, 21 May 2016 13:49:26 +0300 [thread overview]
Message-ID: <87mvnj8z49.fsf@gmail.com> (raw)
In-Reply-To: <20160520133833.GA2160@jasmine> (Leo Famulari's message of "Fri, 20 May 2016 09:38:33 -0400")
Leo Famulari (2016-05-20 16:38 +0300) wrote:
> On Fri, May 20, 2016 at 02:02:41PM +0200, Ludovic Courtès wrote:
>> The patch LGTM, but since this is a full-rebuild change, I prefer keep
>> it for the next core-updates cycle. Let’s try not to forget about it.
>
> Should we create "core-updates-next" or something like that? I have a
> few other patches I don't want to forget about either.
Good idea! I agree.
--
Alex
next prev parent reply other threads:[~2016-05-21 10:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 23:09 Challenge substitute servers! Ludovic Courtès
2015-10-20 0:17 ` Daniel Pimentel
2015-10-20 14:38 ` [PATCHES] emacs: Changes for 'guix challenge' Alex Kost
2015-10-20 14:58 ` Ludovic Courtès
2015-10-20 17:40 ` Timestamps in ...-autoloads.el files Alex Kost
2015-10-20 19:38 ` Ludovic Courtès
2015-10-21 13:05 ` Alex Kost
2015-10-21 16:55 ` Ludovic Courtès
2015-11-02 16:50 ` Alex Kost
2015-11-03 13:27 ` Ludovic Courtès
2015-11-14 11:32 ` Alex Kost
2015-11-14 15:03 ` Ludovic Courtès
2015-11-14 20:39 ` Alex Kost
2016-05-11 14:53 ` Alex Kost
2016-05-16 12:45 ` Ludovic Courtès
2016-05-16 20:52 ` Alex Kost
2016-05-17 9:12 ` Ludovic Courtès
2016-05-19 16:29 ` Alex Kost
2016-05-20 12:02 ` Ludovic Courtès
2016-05-20 13:38 ` Leo Famulari
2016-05-21 10:49 ` Alex Kost [this message]
2016-05-21 21:02 ` Ludovic Courtès
2016-05-24 9:07 ` Alex Kost
2016-05-20 21:14 ` Alex Kost
2016-05-19 8:12 ` Alex Kost
2016-05-19 12:56 ` Ludovic Courtès
2016-05-21 10:31 ` Alex Kost
2016-05-21 21:01 ` Ludovic Courtès
2016-05-24 9:00 ` Alex Kost
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=87mvnj8z49.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).