From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com,
tromey@redhat.com, mark.kettenis@xs4all.nl
Subject: Re: Notes on -Wshadow patches
Date: Sun, 27 Nov 2011 21:24:00 -0000 [thread overview]
Message-ID: <CAHQ1cqES8S0KkANxC3X+9G-f2E82NcE-KRmZkYk=KX5dj=Eg5Q@mail.gmail.com> (raw)
In-Reply-To: <E1RUeSM-0003Dc-Jd@fencepost.gnu.org>
> Doesn't git support generation of ChangeLog entries from commit
> messages? I thought it did. If it does, you should be able to
> generate ChangeLog entries automatically.
>
Not that that I'm an exprt on git, but, no, I am unaware of such
functionality. But it doesn't matter, since, as I said, commit
messages already contain what is to be later added to the changelog, i
just didn't add that to the actual ChangeLog file and therefore it is
not in the diff.
Andrey Smirnov
next prev parent reply other threads:[~2011-11-27 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 12:27 Andrey Smirnov
2011-11-27 13:07 ` Eli Zaretskii
2011-11-27 14:15 ` Mark Kettenis
2011-11-27 20:55 ` Andrey Smirnov
2011-11-27 21:24 ` Andrey Smirnov [this message]
2011-11-27 21:52 ` Joel Brobecker
2011-11-27 17:59 ` Joel Brobecker
2011-11-27 21:17 ` Andrey Smirnov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHQ1cqES8S0KkANxC3X+9G-f2E82NcE-KRmZkYk=KX5dj=Eg5Q@mail.gmail.com' \
--to=andrew.smirnov@gmail.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=tromey@redhat.com \
/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