From: Tom Tromey <tromey@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] dwarf2_physname
Date: Fri, 18 Sep 2009 22:34:00 -0000 [thread overview]
Message-ID: <m3eiq3c26o.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4AB14A38.6000903@redhat.com> (Keith Seitz's message of "Wed, 16 Sep 2009 13:27:36 -0700")
>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
Keith> Tom has suggested to me to conform and start posting bigger bits of
Keith> the patches. Unless I hear anything to the contrary, I'll consider
Keith> this a general approval of the approach, and I will attempt to submit
Keith> any outstanding isolated patches before posting the whole (ginormous)
Keith> patch which implements everything.
What people have done here in the past is just send a big patch series
1..N, with "patch" 0/N explaining the overview to any potential readers.
Sometimes folks also post the mega-patch as well.
I think this has worked pretty well in practice.
I also think it is ok if one patch is a lot bigger than the others. It
doesn't always make sense to try to split things up too much, it just
depends on the problem.
Tom
next prev parent reply other threads:[~2009-09-18 22:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 22:51 Keith Seitz
2009-08-31 23:10 ` Michael Eager
2009-08-31 23:23 ` Keith Seitz
2009-08-31 23:35 ` Michael Eager
2009-09-01 22:11 ` Daniel Jacobowitz
2009-09-01 22:27 ` Daniel Jacobowitz
2009-09-01 23:18 ` Michael Eager
2009-09-01 23:37 ` Daniel Jacobowitz
2009-09-02 1:12 ` Michael Eager
2009-09-01 23:26 ` Keith Seitz
2009-09-01 23:42 ` Daniel Jacobowitz
2009-09-14 18:39 ` Keith Seitz
2009-09-14 22:48 ` Daniel Jacobowitz
2009-09-14 23:56 ` Keith Seitz
2009-09-15 13:32 ` Daniel Jacobowitz
2009-09-15 15:53 ` Keith Seitz
2009-09-15 16:12 ` Daniel Jacobowitz
2009-09-16 20:27 ` Keith Seitz
2009-09-18 22:34 ` Tom Tromey [this message]
[not found] ` <m37hwjy2tl.fsf@fleche.redhat.com>
2009-09-01 0:06 ` Michael Eager
2009-09-01 21:27 ` Tom Tromey
2009-09-01 22:10 ` Keith Seitz
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=m3eiq3c26o.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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