bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>
Subject: Re: [PATCH] vcs-to-changelog: Add manual documentation
Date: Thu, 16 Jan 2020 21:35:06 +0100	[thread overview]
Message-ID: <1956095.NXJGa6zo1W@omega> (raw)
In-Reply-To: <20200116080300.67462-1-siddhesh@gotplt.org>

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).

Bruno



  reply	other threads:[~2020-01-16 20:35 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 [this message]
2020-01-17  3:38   ` Siddhesh Poyarekar
2020-01-18 18:33     ` Bruno Haible
2020-01-19  4:37       ` Siddhesh Poyarekar

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=1956095.NXJGa6zo1W@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=siddhesh@gotplt.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).