bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: [PATCH] vcs-to-changelog: Add manual documentation
Date: Sun, 19 Jan 2020 10:07:29 +0530	[thread overview]
Message-ID: <5f4d493a-b2b5-b7d5-4b32-917bfaf56a43@gotplt.org> (raw)
In-Reply-To: <1776631.Cz6C2zP8Jg@omega>

On 19/01/20 12:03 am, Bruno Haible wrote:
> Hi Siddhesh,
> 
>>>> 	* doc/vcs-to-changelog.texi: New file.
>>>> 	* doc/gnulib.texi (Build Infrastructure Modules): Add
>>>> 	vcs-to-changelog section.
>>>
>>> Thanks. Applied, with a change to the license notice:
>>>
>>>> +@c Texts.  A copy of the license is included in the ``GNU Free
>>>> +@c Documentation License'' file as part of this distribution.
>>>
>>> "as part of this distribution" is not really applicable, since the gnulib
>>> manual is never included in a tarball. I copied the license notice from
>>> gnulib.texi instead (also GFDL 1.3).
>>
>> Thanks, I think I copied from some other source file in gnulib.
> 
> Ah, I see.
> 
> John Darrington pointed out to me two months ago that it is quite frequent that
> individual files get copied out of the original package and out of the original
> git repository. The license notices should cater about this; they should neither
> refer to a "file as part of this distribution" nor to "the section entitled ..."
> if that section is not in the same file. The best way to handle this is a URL.
> Nowadays you can assume that people normally have an internet connection.
> 

Agreed, that makes sense.

Thanks,
Siddhesh


      reply	other threads:[~2020-01-19  4:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16  8:03 [PATCH] vcs-to-changelog: Add manual documentation Siddhesh Poyarekar
2020-01-16 20:35 ` Bruno Haible
2020-01-17  3:38   ` Siddhesh Poyarekar
2020-01-18 18:33     ` Bruno Haible
2020-01-19  4:37       ` Siddhesh Poyarekar [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

  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=5f4d493a-b2b5-b7d5-4b32-917bfaf56a43@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=bruno@clisp.org \
    --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).