From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: [PATCH] Script to generate ChangeLog-like output from git metadata
Date: Tue, 19 Nov 2019 10:20:37 +0530 [thread overview]
Message-ID: <47ae8722-aa82-3936-8769-b3afcd409fd8@gotplt.org> (raw)
In-Reply-To: <27143096.AIZaN4h92k@omega>
On 19/11/19 2:18 am, Bruno Haible wrote:
> Hi Siddhesh,
>
> The first line of build-aux/vcstocl/frontend_c.py:
> #!/usr/bin/python3
>
> But this file is not marked executable and does not contain a __main__
> function.
Opps, sorry, that looks like a copy-paste error. I'll fix that too.
Siddhesh
next prev parent reply other threads:[~2019-11-19 4:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 1:28 [PATCH] Script to generate ChangeLog-like output from git metadata Siddhesh Poyarekar
2019-11-18 20:46 ` Bruno Haible
2019-11-19 4:45 ` Siddhesh Poyarekar
2019-11-18 20:48 ` Bruno Haible
2019-11-19 4:50 ` Siddhesh Poyarekar [this message]
2019-11-18 21:00 ` Bruno Haible
2019-11-19 4:50 ` 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=47ae8722-aa82-3936-8769-b3afcd409fd8@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).