all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: 69129@debbugs.gnu.org
Subject: bug#69129: sbcl-mcclim broke on upgrade to sbcl@2.4.0
Date: Sun, 18 Feb 2024 14:14:26 +1100	[thread overview]
Message-ID: <878r3ixy3x.fsf@zancanaro.id.au> (raw)
In-Reply-To: <87zfvzl02q.fsf@gmail.com> (Sharlatan Hellseher's message of "Sat, 17 Feb 2024 12:58:05 +0000")

On Sat, Feb 17 2024, Sharlatan Hellseher wrote:
> I've added copyright header and use version field for commit.

Thanks for that. I feel like this work was entirely mechanical, so I
would have been fine without a copyright header, but I appreciate it.

I'm curious about the version/commit change, though. Given the -yule
suffix on the tag name changes with each version we will still need to
manually update the origin's commit. It feels like unnecessary
indirection to me. What is the benefit to referencing the package's
version in the origin like this?

Carlo




  reply	other threads:[~2024-02-18  3:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 17:29 bug#69129: sbcl-mcclim broke on upgrade to sbcl@2.4.0 Christopher Howard
2024-02-15 10:28 ` Guillaume Le Vaillant
2024-02-15 15:31   ` Christopher Howard
2024-02-16 19:40     ` Guillaume Le Vaillant
2024-02-17 11:24       ` bug#69129: [PATCH] gnu: sbcl-mcclim: Update to 0.9.8 Carlo Zancanaro
2024-02-17 11:40         ` Sharlatan Hellseher
2024-02-17 12:02           ` bug#69129: [PATCH v2 1/2] " Carlo Zancanaro
2024-02-17 12:02           ` bug#69129: [PATCH v2 2/2] gnu: sbcl-mcclim: Reformatting Carlo Zancanaro
2024-02-17 12:58 ` bug#69129: sbcl-mcclim broke on upgrade to sbcl@2.4.0 Sharlatan Hellseher
2024-02-18  3:14   ` Carlo Zancanaro [this message]
2024-02-18 14:35 ` Sharlatan Hellseher

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=878r3ixy3x.fsf@zancanaro.id.au \
    --to=carlo@zancanaro.id.au \
    --cc=69129@debbugs.gnu.org \
    --cc=sharlatanus@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.