From: Doug Evans <dje@google.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Allow gdbserver to dynamically lookup libthread_db.so.1
Date: Wed, 02 Sep 2009 17:19:00 -0000 [thread overview]
Message-ID: <e394668d0909021019i51fa57d0qa3f5d41c61b26b1b@mail.gmail.com> (raw)
In-Reply-To: <8ac60eac0909021015u37d1a6e2u1ae88dd35d00d2b9@mail.gmail.com>
On Wed, Sep 2, 2009 at 10:15 AM, Paul Pluzhnikov<ppluzhnikov@google.com> wrote:
> Given gdbserver/acinclude.m4 change, I should include gdbserver/configure
> change here, but not gdbserver/configure.ac, right?
Data point: It is not necessary to include changes to generated files
in patches.
Some even prefer to not include them, less noise in the patch.
next prev parent reply other threads:[~2009-09-02 17:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 16:34 Paul Pluzhnikov
2009-09-02 16:43 ` Paul Pluzhnikov
2009-09-02 16:47 ` Pedro Alves
2009-09-02 17:16 ` Paul Pluzhnikov
2009-09-02 17:19 ` Doug Evans [this message]
2009-10-02 23:51 ` Paul Pluzhnikov
2009-10-04 20:32 ` Pedro Alves
2009-10-05 1:49 ` Paul Pluzhnikov
2009-10-05 3:03 ` Pedro Alves
2009-10-13 13:53 ` Pedro Alves
2009-10-06 23:08 ` Paul Pluzhnikov
2009-10-06 23:44 ` Pedro Alves
2009-10-07 0:27 ` Paul Pluzhnikov
2009-10-08 18:08 ` Pedro Alves
2009-10-08 19:05 ` Daniel Jacobowitz
2009-10-08 19:21 ` Paul Pluzhnikov
2009-10-08 19:42 ` Daniel Jacobowitz
2009-10-16 0:41 ` Paul Pluzhnikov
2009-10-22 21:03 ` Paul Pluzhnikov
2009-10-29 16:52 ` Paul Pluzhnikov
2009-10-29 17:27 ` Daniel Jacobowitz
2009-10-29 17:45 ` Paul Pluzhnikov
2009-10-08 19:36 ` Paul Pluzhnikov
2009-10-08 22:58 ` Pedro Alves
2009-10-04 20:34 ` Pedro Alves
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=e394668d0909021019i51fa57d0qa3f5d41c61b26b1b@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=ppluzhnikov@google.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