unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Zac Berkowitz <zac.berkowitz@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 55874@debbugs.gnu.org
Subject: [bug#55874] [PATCH] Add timewarrior 1.4.3
Date: Thu, 9 Jun 2022 21:36:58 -0400	[thread overview]
Message-ID: <CANNGBfkQGne5VV2CjT8OqtKb4-2BBm1g+19w3qnrEEYDYC5qCw@mail.gmail.com> (raw)
In-Reply-To: <56ba51f3df6a70e78518630ad45c3dfc07fdd2a9.camel@telenet.be>

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?

Cheers,

Zac

On Thu, Jun 9, 2022 at 4:17 PM Maxime Devos <maximedevos@telenet.be> wrote:
>
> According to archlinux, there are some bogus man pages:
>
> https://archlinuxarm.org/packages/aarch64/timew/files/PKGBUILD
>
> are they absent here?  (Also, archlinux has the same hash!)




  reply	other threads:[~2022-06-10  1:38 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 [this message]
2022-06-10  7:49     ` Maxime Devos
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

  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=CANNGBfkQGne5VV2CjT8OqtKb4-2BBm1g+19w3qnrEEYDYC5qCw@mail.gmail.com \
    --to=zac.berkowitz@gmail.com \
    --cc=55874@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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).