unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>,
	Maxime Devos <maximedevos@telenet.be>,
	Olivier Dion <olivier.dion@polymtl.ca>
Cc: 56149@debbugs.gnu.org
Subject: [bug#56149] [maintenance PATCH 1/2] talks: Add JRES 2022 tutorial.
Date: Mon, 20 Jun 2022 05:57:41 +0200	[thread overview]
Message-ID: <CAJ3okZ1Yi2r-DNXu1_AGCaAtzp+6OwPg8yzpRV36BFouPtWCUw@mail.gmail.com> (raw)
In-Reply-To: <87o7yko93y@nckx>

Hi,

On Wed, 22 Jun 2022 at 20:17, Tobias Geerinckx-Rice <me@tobias.gr> wrote:

> Wow.  I'm curious if anyone *didn't* experience this as an
> unscheduled MUA stress test :-)

Oops! :-)


> Anyway, applied as 70d972ea83778990f1c0f1701d6a6dada242c2b7 et al.

Thanks!


On Wed, 22 Jun 2022 at 17:34, Olivier Dion <olivier.dion@polymtl.ca> wrote:
>
> Do you think it's possible to avoid git-diff of png in email?  Notmuch in
> emacs is very slow in that case.

Do you an alternative way?  Because I do not know how to send
appliable patches without using git-diff by email; and when I prepare
some presentation, I am doing what is the most suitable for the very
same presentation and not what is the most suitable for the later
patches.

(Note that the patches are against the repo 'maintenance' as mentioned
in the subject; repo with few commits.)


Cheers,
simon




      reply	other threads:[~2022-06-23  7:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  3:51 [bug#56149] [maintenance PATCH 1/2] talks: Add JRES 2022 tutorial zimoun
2022-06-20  3:54 ` [bug#56149] [maintenance PATCH 2/2] talks: Add INRAE workshop 2022 zimoun
2022-06-24 15:01   ` Ludovic Courtès
2022-06-22 15:34 ` [bug#56149] [maintenance PATCH 1/2] talks: Add JRES 2022 tutorial Olivier Dion via Guix-patches via
2022-06-22 16:51   ` Maxime Devos
2022-06-22 18:13 ` Tobias Geerinckx-Rice via Guix-patches via
2022-06-20  3:57   ` zimoun [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=CAJ3okZ1Yi2r-DNXu1_AGCaAtzp+6OwPg8yzpRV36BFouPtWCUw@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=56149@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=me@tobias.gr \
    --cc=olivier.dion@polymtl.ca \
    /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).