From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mdBook: update to 0.4.29
Date: Wed, 24 May 2023 22:17:44 +0200 [thread overview]
Message-ID: <20230524201744.Dd0whhZTBSnH_pSpuvf7DRBETuD1ftlgyuLVN1u0nmY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44055@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/44055#issuecomment-1561873260
Comment:
`.../archive/<some ref>.tar.gz` works so long as there is no branch (or other ref) with the same name as the tag we want. when it doesn't work, the failure mode is something like "multiple refs match". using `.../archive/refs/tags/<some tag>.tar.gz` ensures that we only ever grab a tag ref
next prev parent reply other threads:[~2023-05-24 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 20:57 [PR PATCH] " cinerea0
2023-05-24 18:30 ` Vaelatern
2023-05-24 20:17 ` classabbyamp [this message]
2023-05-24 20:42 ` [PR PATCH] [Merged]: " Vaelatern
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=20230524201744.Dd0whhZTBSnH_pSpuvf7DRBETuD1ftlgyuLVN1u0nmY@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).