From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Move gnulib to top level
Date: Fri, 14 Jun 2019 19:02:00 -0000 [thread overview]
Message-ID: <87blz0m1lz.fsf@tromey.com> (raw)
In-Reply-To: <87ef3x8hcw.fsf@tromey.com> (Tom Tromey's message of "Thu, 13 Jun 2019 12:34:07 -0600")
Tom> I'll commit it soon, probably tomorrow morning.
I did this.
You will probably need to do a clean build.
Tom
next prev parent reply other threads:[~2019-06-14 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 12:48 Tom Tromey
2019-06-13 13:29 ` Pedro Alves
2019-06-13 18:34 ` Tom Tromey
2019-06-14 19:02 ` Tom Tromey [this message]
2019-06-19 15:56 ` Tom de Vries
2019-06-21 13:00 ` Tom Tromey
2019-06-21 13:23 ` Andreas Schwab
2019-06-21 14:56 ` Tom Tromey
2019-07-30 18:20 ` in-src-tree build regression [Re: [PATCH] Move gnulib to top level] Jan Kratochvil
2019-07-31 17:30 ` Tom Tromey
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=87blz0m1lz.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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