unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 44039@debbugs.gnu.org, James Smith <jsubuntuxp@disroot.org>,
	James Smith <jsubuntuxp@gmail.com>
Subject: [bug#44039] [PATCH] gnu: Add slade.
Date: Fri, 30 Oct 2020 10:38:42 +0100	[thread overview]
Message-ID: <87r1pgnjdp.fsf@nckx> (raw)
In-Reply-To: <87v9esy52t.fsf@gnu.org>

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

Ludovic Courtès 写道：
> Like I wrote, it seems that v2 mostly fits the bill.  The only 
> potential
> issue as I see it is the new ‘reset-slade.pk3-timestamps’ phase: 
> I don’t
> see what effect it has, like I wrote, so I wonder if it’s 
> necessary.

I need more information to have any opinion :-)

What are you looking at to gauge its effects?  You seem to be 
claiming it has none for you, is that correct?

I build on tmpfs BTW.  Perhaps other file systems could introduce 
more ‘fun’.

Kind regards,

T G-R

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

  reply	other threads:[~2020-10-30  9:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 18:43 [bug#44039] [PATCH] gnu: Add slade James Smith
2020-10-16 21:07 ` Tobias Geerinckx-Rice via Guix-patches via
2020-10-16 21:14   ` Tobias Geerinckx-Rice via Guix-patches via
2020-10-17  0:41   ` James Smith
2020-10-28 14:54   ` Ludovic Courtès
2020-10-29  2:49     ` James Smith
2020-10-29 23:39       ` Ludovic Courtès
2020-10-30  9:38         ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-10-31 10:01           ` Ludovic Courtès
2021-05-15 20:52 ` James Smith
2021-09-18 17:47 ` [bug#44039] [PATCH v3] " James Smith via Guix-patches via
2021-09-22 14:21   ` bug#44039: [PATCH] " Ludovic Courtès

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=87r1pgnjdp.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=44039@debbugs.gnu.org \
    --cc=jsubuntuxp@disroot.org \
    --cc=jsubuntuxp@gmail.com \
    --cc=ludo@gnu.org \
    --cc=me@tobias.gr \
    /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).