all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: 69827@debbugs.gnu.org
Subject: [bug#69827] [PATCH 1/3] build-system/go: Add subdir parameter to go-version->git-ref.
Date: Tue, 16 Apr 2024 20:05:29 +0100	[thread overview]
Message-ID: <CAO+9K5rZTV+JCfnv+8906gMk2P8L9J4JH_ACt_kjwXj4dfvctw@mail.gmail.com> (raw)
In-Reply-To: <bfb6cb47bc6e2a05846653ca0b07470d4ae8ae05.1710584715.git.cdo@mutix.org>

[-- Attachment #1: Type: text/plain, Size: 287 bytes --]

Hi,

Just a clarifying question. Do we definitely need to know
 anything about the folder structure where go.mod governs the
 module definition?

There is an API https://pkg.go.dev/  where the most of go projects
 are registered, would it be easier just query it directly?

Thanks,
Oleg

[-- Attachment #2: Type: text/html, Size: 625 bytes --]

  parent reply	other threads:[~2024-04-16 19:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16 10:26 [bug#69827] [PATCH 1/3] build-system/go: Add subdir parameter to go-version->git-ref Christina O'Donnell
2024-03-16 10:30 ` [bug#69827] [PATCH 2/3] import/go: Account for monorepo modules in the Go importer Christina O'Donnell
2024-03-16 10:30 ` [bug#69827] [PATCH 3/3] import/go: Add diagnostics Christina O'Donnell
2024-03-16 10:45 ` [bug#69827] Fixing the go importer so that it can import modules located in a monorepo Christina O'Donnell
2024-04-16 19:05 ` Sharlatan Hellseher [this message]
2024-05-11 12:04 ` [bug#69827] [PATCH 1/3] build-system/go: Add subdir parameter to go-version->git-ref Christina O'Donnell
2024-09-04 19:18 ` Sharlatan Hellseher
2024-09-07 14:28 ` Sharlatan Hellseher
2024-09-10 12:21   ` Simon Tournier
2024-09-15 20:40 ` bug#69827: " 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=CAO+9K5rZTV+JCfnv+8906gMk2P8L9J4JH_ACt_kjwXj4dfvctw@mail.gmail.com \
    --to=sharlatanus@gmail.com \
    --cc=69827@debbugs.gnu.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. 
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.