This is the mail archive of the
mailing list for the GDB project.
Re: [pushed] [PATCH V7 0/8] Intel(R) MPX register support
- From: Tom Tromey <tromey at redhat dot com>
- To: "Tedeschi\, Walfred" <walfred dot tedeschi at intel dot com>
- Cc: Pedro Alves <palves at redhat dot com>, Yao Qi <yao at codesourcery dot com>, "Mark Kettenis \(mark dot kettenis\ at xs4all dot nl\)" <mark dot kettenis at xs4all dot nl>, "gdb-patches\ at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Fri, 22 Nov 2013 10:16:05 -0700
- Subject: Re: [pushed] [PATCH V7 0/8] Intel(R) MPX register support
- Authentication-results: sourceware.org; auth=none
- References: <AC542571535E904D8E8ADAE745D60B191B1D8BC7 at IRSMSX104 dot ger dot corp dot intel dot com> <528E62B3 dot 7080005 at redhat dot com> <AC542571535E904D8E8ADAE745D60B191B1D9C3D at IRSMSX104 dot ger dot corp dot intel dot com>
>>>>> ">" == Tedeschi, Walfred <firstname.lastname@example.org> writes:
>> BTW: Next patch we will squash i386/amd64/gdbserver. Should this three
>> patches also be send for review as a single commit?
Usually it's best to make each patch work independently. This is the
ideal because then one doesn't need to do anything special when
submitting or merging.
Of course, it isn't always possible. Sometimes a patch is easier to
read when split, but the split means that some sub-patch doesn't build.
In this case I think it is fine to note the issue in the email and then
remember to squash the relevant patches at merge time.