Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] package/libmodplug: use a full-length hash as version
Date: Fri, 13 Oct 2023 17:04:03 +0200	[thread overview]
Message-ID: <8734ye4l98.fsf@48ers.dk> (raw)
In-Reply-To: <20231001195516.9BA4383F9E@busybox.osuosl.org> (Yann E. MORIN's message of "Sun, 1 Oct 2023 21:52:12 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > commit: https://git.buildroot.net/buildroot/commit/?id=80e94c76169fd15d2433b18a9e54d6a4f3c4ff18
 > branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master

 > Commit 369ff9a88ff8 (package/libmodplug: update to git version)
 > improperly used a short hash as version, so switch to the full-length
 > hash.

 > Github use the full-length hash when it creates the top-level directory
 > of the generated archive, so the hash of the archive does not in fact
 > change, only its filename. This is perfectly fine fine our handling of
 > s.b.o.

 > Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>

Committed to 2023.02.x and 2023.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-10-13 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01 19:52 [Buildroot] [git commit] package/libmodplug: use a full-length hash as version Yann E. MORIN
2023-10-13 15:04 ` Peter Korsgaard [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8734ye4l98.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox