unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: zimoun <zimon.toutoune@gmail.com>, "John Soo" <jsoo1@asu.edu>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: 43929 <43929@debbugs.gnu.org>
Subject: [bug#43929] gnu: Add pijul.
Date: Wed, 28 Oct 2020 13:37:31 -0400	[thread overview]
Message-ID: <2DFC6265-699A-4EA3-8E50-5352B8EA59F6@lepiller.eu> (raw)
In-Reply-To: <864kme2w8g.fsf@gmail.com>



Le 28 octobre 2020 11:42:07 GMT-04:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>Hi,
>
>On Wed, 28 Oct 2020 at 08:13, John Soo <jsoo1@asu.edu> wrote:
>  
>> I have been busy rebasing these patches.  I may have a new set this
>> week
>
>It could be cool if it could be included in the v1.2. :-)
>
>
>> Also pijul 2 is coming very soon. Should I wait to submit that
>> instead? 
>
>From my point of view, because of the “time-machine”, it is nice to
>include any version – especially when it is already done. :-)

Yeah I agree, you don't have to wait, since you already have everything available :)

Sorry I didn't do a review, I ended up being busy with work and other things.

>
>
>Cheers,
>simon




  reply	other threads:[~2020-10-28 17:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11 16:58 [bug#43929] gnu: Add pijul John Soo
2020-10-11 17:40 ` Julien Lepiller
2020-10-28 14:57   ` Ludovic Courtès
2020-10-28 15:13     ` John Soo
2020-10-28 15:42       ` zimoun
2020-10-28 17:37         ` Julien Lepiller [this message]
2020-10-31 18:15           ` John Soo
2020-11-22 16:34             ` Efraim Flashner
2020-11-22 16:45               ` John Soo
2020-10-31 18:31           ` John Soo
2020-11-05 16:16           ` John Soo
2020-11-25 15:43             ` John Soo
2021-02-15 22:18               ` John Soo
2021-02-16  9:31                 ` Nicolas Goaziou

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=2DFC6265-699A-4EA3-8E50-5352B8EA59F6@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=43929@debbugs.gnu.org \
    --cc=jsoo1@asu.edu \
    --cc=ludo@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).