all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Raghav Gururajan <rg@raghavgururajan.name>, 46653-done@debbugs.gnu.org
Subject: bug#46653: Make some changes to Profanity stuff (v4)
Date: Wed, 24 Feb 2021 01:02:00 +0100	[thread overview]
Message-ID: <526ee0970b3a580cd7eca3de171d50c424c123b4.camel@student.tugraz.at> (raw)
In-Reply-To: <1c4c1c15-9230-1991-78d6-1fbbc322ebd5@raghavgururajan.name>

Hi Raghav,

Am Dienstag, den 23.02.2021, 15:01 -0500 schrieb Raghav Gururajan:
> Hi Leo!
> 
> > Great, now re-order them again so that no patch causes a rebuild of
> > a
> > formerly patched package.
> 
> Done in v4.
> 
> > > That would be 3 tests.
> > 3 of how many?  And how many on the other package?
> Tests are now fixed in v4, with the help of Tobias.
Thanks!  Pushed with some cosmetic changes.

Regards,
Leo





      reply	other threads:[~2021-02-24  0:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20  3:08 [bug#46653] Make some changes to Profanity stuff Raghav Gururajan via Guix-patches via
     [not found] ` <handler.46653.B.161379050225230.ack@debbugs.gnu.org>
2021-02-23 17:08   ` [bug#46653] Make some changes to Profanity stuff (v2) Raghav Gururajan via Guix-patches via
2021-02-23 17:28     ` Leo Prikler
2021-02-23 17:32       ` Raghav Gururajan via Guix-patches via
2021-02-23 17:39         ` Leo Prikler
2021-02-23 17:41           ` Raghav Gururajan via Guix-patches via
2021-02-23 17:48             ` [bug#46653] Make some changes to Profanity stuff (v3) Raghav Gururajan via Guix-patches via
2021-02-23 18:01               ` Leo Prikler
2021-02-23 20:01                 ` [bug#46653] Make some changes to Profanity stuff (v4) Raghav Gururajan via Guix-patches via
2021-02-24  0:02                   ` Leo Prikler [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

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

  git send-email \
    --in-reply-to=526ee0970b3a580cd7eca3de171d50c424c123b4.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=46653-done@debbugs.gnu.org \
    --cc=rg@raghavgururajan.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.