From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: joseph@codesourcery.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: switch to autogenerated ChangeLog files
Date: Tue, 12 Jan 2021 20:40:51 +0200 [thread overview]
Message-ID: <83im82c824.fsf@gnu.org> (raw)
In-Reply-To: <83o8huc8o3.fsf@gnu.org> (message from Eli Zaretskii via Gdb-patches on Tue, 12 Jan 2021 20:27:40 +0200)
> Date: Tue, 12 Jan 2021 20:27:40 +0200
> From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
> Cc: gdb-patches@sourceware.org
>
> Please check out the latest text (maybe it is still only in CVS, not
> on prep, I don't keep track of that).
Actually, I now see that the version on prep is also up-to-date with
those changes.
next prev parent reply other threads:[~2021-01-12 18:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 3:37 [PATCH 1/3] src-release: fix indentation Mike Frysinger via Gdb-patches
2021-01-10 3:37 ` [PATCH 2/3] gnulib: import gitlog-to-changelog Mike Frysinger via Gdb-patches
2021-01-11 11:06 ` Andrew Burgess
2021-01-10 3:42 ` [PATCH] sim: switch to autogenerated ChangeLog files Mike Frysinger via Gdb-patches
2021-01-11 11:05 ` Andrew Burgess
2021-01-11 17:00 ` Simon Marchi via Gdb-patches
2021-01-11 17:10 ` Luis Machado via Gdb-patches
2021-01-11 17:31 ` Christian Biesinger via Gdb-patches
2021-01-11 19:38 ` Mike Frysinger via Gdb-patches
2021-01-11 19:54 ` Simon Marchi via Gdb-patches
2021-01-11 20:35 ` Mike Frysinger via Gdb-patches
2021-01-12 10:47 ` Andrew Burgess
2021-01-12 18:14 ` Joseph Myers
2021-01-12 18:27 ` Eli Zaretskii via Gdb-patches
2021-01-12 18:40 ` Eli Zaretskii via Gdb-patches [this message]
2021-01-12 21:27 ` Mike Frysinger via Gdb-patches
2021-01-12 21:22 ` Mike Frysinger via Gdb-patches
2021-03-09 5:51 ` Mike Frysinger via Gdb-patches
2021-03-09 9:42 ` Andrew Burgess
2021-03-17 14:22 ` Luis Machado via Gdb-patches
2021-01-12 23:20 ` [PATCH 1/3] src-release: fix indentation Mike Frysinger via Gdb-patches
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=83im82c824.fsf@gnu.org \
--to=gdb-patches@sourceware.org \
--cc=eliz@gnu.org \
--cc=joseph@codesourcery.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