From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Asher Gordon <AsDaGo@posteo.net>
Subject: Re: Remove license modules
Date: Sat, 16 May 2020 01:17:40 +0200 [thread overview]
Message-ID: <3987483.8Pq7tfHfNr@omega> (raw)
In-Reply-To: <873685hwin.fsf@posteo.net>
Hi,
Asher Gordon wrote:
> Since Savannah requires licenses to be under version control (see
> here¹), I don't think it makes sense for Gnulib to provide modules for
> them. My reasoning is that if developers are going to use a Gnulib
> module, they won't keep the files it provides under version control (in
> fact, gnulib-tool itself adds these files to .gitignore). There's no
> reason to remove the license *files*, since it could be useful for
> developers to copy them directly.
> ...
> Footnotes:
> ¹ https://savannah.nongnu.org/task/?func=detailitem&item_id=15583
At the moment you sent the mail, the discussion in that ticket was still
ongoing.
Now it has completed, and it turned out you were confusing the license
texts in text format (which ought to be added to VCS directly) and the
license texts in Texinfo format (for which gnulib modules are appropriate).
Bruno
next prev parent reply other threads:[~2020-05-15 23:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 17:51 Remove license modules Asher Gordon
2020-05-15 23:17 ` Bruno Haible [this message]
2020-05-16 18:03 ` Asher Gordon
2020-05-17 17:39 ` Bruno Haible
2020-05-17 19:58 ` Asher Gordon
2020-05-17 20:12 ` Asher Gordon
2020-06-01 18:00 ` Bruno Haible
2020-06-01 18:09 ` Paul Eggert
2020-06-01 19:06 ` Typographical errors in Texinfo format licenses Asher Gordon
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.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3987483.8Pq7tfHfNr@omega \
--to=bruno@clisp.org \
--cc=AsDaGo@posteo.net \
--cc=bug-gnulib@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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).