unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Tomas Volf <~@wolfsden.cz>
Cc: 74821@debbugs.gnu.org
Subject: [bug#74821] [PATCH] gnu: cgit: Update to 1.2.3-7.751a5b5.
Date: Tue, 17 Dec 2024 10:24:42 +0900	[thread overview]
Message-ID: <87msgvrtid.fsf@gmail.com> (raw)
In-Reply-To: <1a8790d643cc3171d765ec483e99fe1e831747e5.1734003995.git.~@wolfsden.cz> (Tomas Volf's message of "Thu, 12 Dec 2024 12:46:35 +0100")

Hi Tomas,

Tomas Volf <~@wolfsden.cz> writes:

> * gnu/packages/version-control.scm (cgit): Update to 1.2.3-7.751a5b5.
>
> Change-Id: I3f4d27246065d67a258a8cf3b3dea2e0b2d2bc9f
> ---
>  gnu/packages/version-control.scm | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/gnu/packages/version-control.scm b/gnu/packages/version-control.scm
> index 3339e79390..28afcfa2ff 100644
> --- a/gnu/packages/version-control.scm
> +++ b/gnu/packages/version-control.scm
> @@ -1345,8 +1345,8 @@ (define-public git-remote-gcrypt
>     (license license:gpl3+)))
>

Usually, we request that a comment is added to explain why a particular
unreleased commit must be used instead of the latest release.  Would it
be possible to remove the commit/rev variables and switch back to use
the latest release?  It's not clear why we aren't doing that.

-- 
Thanks,
Maxim




      reply	other threads:[~2024-12-17  1:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 11:46 [bug#74821] [PATCH] gnu: cgit: Update to 1.2.3-7.751a5b5 Tomas Volf
2024-12-17  1:24 ` Maxim Cournoyer [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=87msgvrtid.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=74821@debbugs.gnu.org \
    --cc=~@wolfsden.cz \
    /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).