unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Brice Waegeneire <brice@waegenei.re>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 53920@debbugs.gnu.org
Subject: [bug#53920] [PATCH] gnu: lesspipe: Update to 2.02.
Date: Sat, 12 Feb 2022 10:48:27 +0100	[thread overview]
Message-ID: <87r188wh3o.fsf@waegenei.re> (raw)
In-Reply-To: <639f99264ee673157112aec54d28c80842e4be52.1644511905.git.h.goebel@crazy-compilers.com> (Hartmut Goebel's message of "Thu, 10 Feb 2022 17:52:31 +0100")

Hello Hartmut,

Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> * gnu/packages/less.scm (lesspipe): Update to 2.02.
> ---
>  gnu/packages/less.scm | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

[...]

Thank you for the patch, I wasn't able to build it tho. Because the previsou git
tag was named "1.91" and the latest one is "v2.02", so the commit field from
git-reference need to be adjusted.  Did you managed to build and test it on your
side before sending the patch?

Cheers,
- Brice




  reply	other threads:[~2022-02-12  9:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 16:52 [bug#53920] [PATCH] gnu: lesspipe: Update to 2.02 Hartmut Goebel
2022-02-12  9:48 ` Brice Waegeneire [this message]
2022-02-20 16:54   ` Hartmut Goebel
2022-02-22 18:42   ` Hartmut Goebel
2022-02-22  9:16 ` [bug#53920] [PATCH v2] " Hartmut Goebel
2022-02-22 18:39 ` [bug#53920] [PATCH v3] gnu: lesspipe: Update to 2.03 Hartmut Goebel
2022-02-27 22:06   ` [bug#53920] [PATCH] gnu: lesspipe: Update to 2.02 Ludovic Courtès
2022-02-27 22:22   ` [bug#53920] [PATCH v3] gnu: lesspipe: Update to 2.03 Maxime Devos
2022-02-28  8:25     ` Hartmut Goebel
2022-02-28  9:56       ` Nicolas Goaziou
2022-02-28 12:31         ` Hartmut Goebel
2022-02-28 12:50           ` Nicolas Goaziou
2022-03-02 20:52             ` bug#53920: " Hartmut Goebel

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=87r188wh3o.fsf@waegenei.re \
    --to=brice@waegenei.re \
    --cc=53920@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.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 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).