This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/5] Updates d_language_defn to not use macro expansion
- From: Tom Tromey <tromey at redhat dot com>
- To: Iain Buclaw <ibuclaw at gdcproject dot org>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 16 Jan 2014 07:34:00 -0700
- Subject: Re: [PATCH 2/5] Updates d_language_defn to not use macro expansion
- Authentication-results: sourceware.org; auth=none
- References: <CABOHX+cJ34G1FA240ZdV8xNsn0fqGezDNcu0aY5k7KZ8=X6_jA at mail dot gmail dot com> <871u0h9g41 dot fsf at fleche dot redhat dot com> <CABOHX+eMZD3xky9axEq1dUTznO0QT5k-GK+-0GUE5W60CrCo4Q at mail dot gmail dot com> <CABOHX+d5u_TZKUtp8eYYrryOLVLwBUgjcdB_VrXDUa14OV8=4Q at mail dot gmail dot com> <8738kv7o9y dot fsf at fleche dot redhat dot com> <CABOHX+cjg+JfZT0CsLxwjrojNTy6AK4w+FBDDrfYOPR1gp_SxQ at mail dot gmail dot com>
>>>>> "Iain" == Iain Buclaw <ibuclaw@gdcproject.org> writes:
Iain> Is there anything else needed to be done from me? Just asking as I
Iain> noticed a change to the way that requires this patch to be updated.
I wasn't keeping score, but if all the patches are approved, you can
rebase (our git repository rejects merge commits on master), merge to
master, and push. If a patch needs any changes during the rebase, you
can use your judgment -- if it is just a trivial change, post the
updated patch as an FYI; if it required some work, usually another round
of review is needed.
If you don't have write-after-approval access, now is a good time to get
it :). Send me email off-list and I will hook you up.
Tom