From: yarl-baudig@mailoo.org
To: liliana.prikler@gmail.com, 55674@debbugs.gnu.org
Subject: [bug#55674] [PATCH] gnu: emacs-helpful: Update to 209971b
Date: Sun, 29 May 2022 11:09:12 +0200 (CEST) [thread overview]
Message-ID: <ea-mime-62933838-600-37890f41@www-7.mailo.com> (raw)
In-Reply-To: <2f5f0d333b8a15a52ba25468cc3d3402229083c2.camel@gmail.com>
> Commit hashes are not versions. Furthermore, there has been more than
> just that bugfix since – as a workaround I think it'd be more
> reasonable to just disable that one test until the next release.
Or Erik Šabič might try its patch against version 0.19 then add it to the package definition and let a comment that as soon as it is updated to 0.20, the patch can go away?
next prev parent reply other threads:[~2022-05-29 9:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 12:52 [bug#55675] [PATCH 1/2] gnu: emacs-elm-mode: Update to 0.21.0-1.1e27768 Erik Šabič
2022-05-27 12:52 ` [bug#55674] [PATCH 2/2] gnu: emacs-helpful: Update to 0.19 Erik Šabič
2022-05-27 13:12 ` Maxime Devos
[not found] ` <CABeAMAkLbQHB_aGAr_Tf8+1DPzjMSW1mKSUH6Zh7fPyZQCAeBg@mail.gmail.com>
2022-05-27 13:48 ` [bug#55675] " Maxime Devos
2022-05-27 17:23 ` Erik Šabič
2022-05-27 14:58 ` [bug#55674] Broken tests Erik Šabič
2022-05-29 5:05 ` [bug#55674] PR accepted yarl-baudig
2022-05-29 5:13 ` [bug#55674] [PATCH] gnu: emacs-helpful: Update to 209971b yarl-baudig
2022-05-29 7:41 ` Liliana Marie Prikler
2022-05-29 9:09 ` yarl-baudig [this message]
2022-05-29 10:12 ` Liliana Marie Prikler
2022-05-30 7:20 ` [bug#55674] [PATCH] gnu: emacs-helpful: Update to 0.19 yarl-baudig
2022-05-30 19:41 ` Liliana Marie Prikler
2022-05-30 21:11 ` yarl baudig
2022-06-04 7:00 ` bug#55674: " Liliana Marie Prikler
2022-05-27 13:21 ` [bug#55675] Question Erik Šabič
2022-05-27 13:49 ` Maxime Devos
2022-05-27 14:27 ` [bug#55675] emacs-dash Erik Šabič
2022-06-05 21:34 ` bug#55675: [PATCH 1/2] gnu: emacs-elm-mode: Update to 0.21.0-1.1e27768 Ludovic Courtès
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=ea-mime-62933838-600-37890f41@www-7.mailo.com \
--to=yarl-baudig@mailoo.org \
--cc=55674@debbugs.gnu.org \
--cc=liliana.prikler@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.