From: Maxime Devos <maximedevos@telenet.be>
To: Zac Berkowitz <zac.berkowitz@gmail.com>
Cc: 55874@debbugs.gnu.org
Subject: [bug#55874] [PATCH] Add timewarrior 1.4.3
Date: Fri, 10 Jun 2022 09:49:40 +0200 [thread overview]
Message-ID: <c78c6132514b8ec6bd68760e3990f915e32748c0.camel@telenet.be> (raw)
In-Reply-To: <CANNGBfkQGne5VV2CjT8OqtKb4-2BBm1g+19w3qnrEEYDYC5qCw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
Zac Berkowitz schreef op do 09-06-2022 om 21:36 [-0400]:
> Maxime,
>
> Thanks for all of the great feedback -- seems like "works for me"
> wasn't nearly good enough in this case! I'll chip away at these
> issues next week when I've got some time. Is submitting a new patch
> on this bug # the best way forward? Or should I close this and open a
> new patch issue when it's ready?
Send it as a v2 to 55874@, then all the relevant information is kept
together at <https://issues.guix.gnu.org/55874>.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-10 7:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 15:11 [bug#55874] [PATCH] Add timewarrior 1.4.3 Zac Berkowitz
2022-06-09 19:50 ` Maxime Devos
2022-06-09 19:53 ` Maxime Devos
2022-06-09 19:55 ` Maxime Devos
2022-06-09 19:56 ` Maxime Devos
2022-06-09 20:01 ` Maxime Devos
2022-06-09 20:06 ` Maxime Devos
2022-06-09 20:08 ` Maxime Devos
2022-06-09 20:09 ` Maxime Devos
2022-06-09 20:10 ` Maxime Devos
2022-06-09 20:12 ` Maxime Devos
2022-06-09 20:17 ` Maxime Devos
2022-06-10 1:36 ` Zac Berkowitz
2022-06-10 7:49 ` Maxime Devos [this message]
2022-06-10 14:04 ` Zac Berkowitz
2022-06-10 14:54 ` Maxime Devos
2022-06-10 14:56 ` Maxime Devos
2022-06-10 15:00 ` Maxime Devos
2022-06-10 15:00 ` Maxime Devos
2022-06-13 18:14 ` [bug#55874] [PATCH v2] " Zac Berkowitz
2023-01-28 10:08 ` bug#55874: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c78c6132514b8ec6bd68760e3990f915e32748c0.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55874@debbugs.gnu.org \
--cc=zac.berkowitz@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 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.