From: "Sebastien Binet" <binet@cern.ch>
To: "galene-list" <galene@lists.galene.org>
Subject: [Galene] Galene tags & webserver API
Date: Mon, 29 Apr 2024 14:36:23 +0200 [thread overview]
Message-ID: <D0WM0N7L8TT7.1M3XLXOERW3YB@cern.ch> (raw)
hi there,
(thanks for Galène! it's a nice project and pion code reference to look at :P)
I have 2 questions:
1) why does the Galene project tags releases with "galene-X.Y.Z" instead of the Go-modules compatible "vX.Y.Z" ?
using "vX.Y.Z" would enable nicer-looking 'require' sections in projects using galene.
2) would you be ok with PRs reducing the amount of global variables in the webserver package ?
I'd like to package a galene webserver inside my binary (and embed.FS a bunch of static files with it: my own "static" hierarchy).
perhaps the answer to both questions is actually rooted in the same reason: one just compiles and runs galene but not import/reuse it ?
cheers,
-s
next reply other threads:[~2024-04-29 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 12:36 Sebastien Binet [this message]
2024-04-29 18:54 ` [Galene] " Juliusz Chroboczek
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
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D0WM0N7L8TT7.1M3XLXOERW3YB@cern.ch \
--to=binet@cern.ch \
--cc=galene@lists.galene.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