From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Timo Wilken" <guix@twilken.net>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 63631@debbugs.gnu.org, 64036@debbugs.gnu.org,
63647@debbugs.gnu.org, 64035@debbugs.gnu.org,
63001@debbugs.gnu.org, 54097@debbugs.gnu.org, wolf@wolfsden.cz
Subject: [bug#64035] bug#63001: bug#63631: [PATCH] import: go: Handle subpackage versioning correctly.
Date: Wed, 16 Aug 2023 17:59:53 +0200 [thread overview]
Message-ID: <875y5ff05i.fsf@gmail.com> (raw)
In-Reply-To: <CTF06XBYWPT0.1MV6QA1B2OB98@lap.twilken.net>
Hi Timo,
On Sat, 17 Jun 2023 at 17:12, "Timo Wilken" <guix@twilken.net> wrote:
>> What would you suggest? Simon?
>
> Here's a brief comparison between Simon's patches and mine -- Simon's seem to
> contain fixes for a couple more things than mine currently does:
>
> 1. Simon sorts available versions in an error message; this can presumably be
> merged independently since it doesn't conflict with other patches.
>
> 2. Simon always prepends a "SUBDIR/" prefix to the tag if found, whereas I try
> to find the plain "vX" tag first, then fall back to "SUBDIR/vX". Judging by
> https://go.dev/ref/mod#vcs-version, Simon's approach seems more correct.
> I'll change my implementation to match and try it out.
>
> 3. For detecting the `module-path-subdirectory' in Simon's patches: that's the
> same approach I used initially, but I found I have to try `(substring
> module-path (string-length import-prefix))' first (to handle e.g.
> cloud.google.com/go/*). This is one of the things I haven't submitted
> yet...
Sorry if I have missed some patches or overlooked something. Do you
plan to send another patch series handling all?
Cheers,
simon
prev parent reply other threads:[~2023-08-16 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 21:18 [bug#63631] [PATCH] import: go: Handle subpackage versioning correctly Timo Wilken
2023-05-21 21:54 ` wolf
2023-05-22 19:11 ` bug#54097: " Timo Wilken
2023-06-14 21:09 ` [bug#63631] " Ludovic Courtès
2023-06-17 15:12 ` bug#63001: bug#63631: " Timo Wilken
2023-08-16 15:59 ` Simon Tournier [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=875y5ff05i.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=54097@debbugs.gnu.org \
--cc=63001@debbugs.gnu.org \
--cc=63631@debbugs.gnu.org \
--cc=63647@debbugs.gnu.org \
--cc=64035@debbugs.gnu.org \
--cc=64036@debbugs.gnu.org \
--cc=guix@twilken.net \
--cc=ludo@gnu.org \
--cc=wolf@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 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.