From: Alan Hayward <Alan.Hayward@arm.com>
To: Omair Javaid <omair.javaid@linaro.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH v2 0/8] Remove XML files from gdbserver
Date: Wed, 24 Jan 2018 12:29:00 -0000 [thread overview]
Message-ID: <B5AC1709-2608-4746-A0FA-43010BA8D4CF@arm.com> (raw)
In-Reply-To: <CANW4E-1wgsRemnF3mH+g_fuw0KuzpmGB=VFGtkn0BUcO+DiZig@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2133 bytes --]
> On 24 Jan 2018, at 10:57, Omair Javaid <omair.javaid@linaro.org> wrote:
>
> Hi Alan,
>
> I am failing to apply your patch series to the latest gdb sources. Apparently, your patch series needs a re-base over most recent gdb sources as there has not been a commit since these patches have been posted.
>
> Generally its a good idea to generate patches using git format-patch and send patches using git send-email. Patches need to be based off the most recent gdb commit that is available at the time of sending them for review. If you use git format-patch to generate patches from your local commits it would become very easy for a reviewer to just apply those patches using "git apply" in their local branches.
>
> Kindly post a patchset that works with a known version of gdb sources in order for your patches to be tested/reviewed upstream.
>
Thatâs odd.
My patches were based off yesterdayâs head (d820e164e4baccacd8d4e7e3761ec547402ae828).
Iâve just rebased my git to the latest head, and I got no conflicts or merge warnings.
Looking at the diff from then until now, I canât see any files that my patch touches.
Happy to repost my rebased patches in the same way, but I suspect thatâs not the issue.
Iâve probably got something missing/wrong in the upper parts of of the email.
Were you having trouble with a particular patch or was it all of them?
Also, how are you getting the patch email from your email client to git?
Iâm sending mails by opening my mail client, writing my comments, then copy/pasting the contents
of a diff downloaded from a local reviewboard. That diff looks identical to a git format-patch or git diff.
Iâve tried applying the first patch of the series to the latest head using both my patch file and contents
of the email, and both work for me.
Iâve just tested git send-mail, and it looks like I need to do some messing around to get that working.
I can look at getting that working.
In the meantime, Iâve pushed this branch to gdb with all my commits:
remotes/origin/users/ahayward/xml
Thanks,
Alan.\x16º&Öéj×!zÊÞ¶êç×tÓIb²Ö«r\x18\x1dnr\x17¬
next prev parent reply other threads:[~2018-01-24 12:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 9:26 Alan Hayward
2018-01-24 9:26 ` [PATCH v2 1/8] Move tdesc header funcs to c file Alan Hayward
2018-01-24 9:27 ` [PATCH v2 2/8] Use tdesc_reg in gxdbserver tdesc Alan Hayward
2018-01-25 13:12 ` Philipp Rudo
2018-01-24 9:28 ` [PATCH v2 3/8] Use tdesc_feature in gdbserver tdesc Alan Hayward
2018-01-25 13:12 ` Philipp Rudo
2018-01-24 9:28 ` [PATCH v2 4/8] Move make_gdb_type functions within file Alan Hayward
2018-01-24 9:29 ` [PATCH v2 5/8] Use tdesc types in gdbserver tdesc Alan Hayward
2018-01-25 13:13 ` Philipp Rudo
2018-01-29 7:28 ` Omair Javaid
2018-01-29 11:01 ` Alan Hayward
[not found] ` <20180129123042.4a1674d6@ThinkPad>
2018-01-29 15:52 ` Alan Hayward
2018-01-24 9:30 ` [PATCH v2 6/8] Create xml from target descriptions Alan Hayward
2018-01-25 13:14 ` Philipp Rudo
2018-01-25 15:45 ` Yao Qi
2018-01-25 16:13 ` Alan Hayward
2018-01-25 16:56 ` Philipp Rudo
2018-01-24 9:31 ` [PATCH v2 7/8]: Remove xml file references " Alan Hayward
2018-01-24 9:32 ` [PATCH v2 8/8] Remove xml files from gdbserver Alan Hayward
2018-01-24 10:57 ` [PATCH v2 0/8] Remove XML " Omair Javaid
2018-01-24 12:29 ` Alan Hayward [this message]
[not found] ` <CANW4E-30Q5zRPrA0Vqe648f4psPqPMUCmSADYRjTK292kZy_Ng@mail.gmail.com>
2018-01-24 18:53 ` Alan Hayward
2018-01-25 13:11 ` Philipp Rudo
2018-01-26 22:31 ` Omair Javaid
2018-01-29 16:28 ` Yao Qi
2018-01-29 17:13 ` Alan Hayward
2018-01-31 11:28 ` Alan Hayward
2018-01-29 18:18 ` Pedro Alves
2018-01-30 12:16 ` Alan Hayward
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=B5AC1709-2608-4746-A0FA-43010BA8D4CF@arm.com \
--to=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=omair.javaid@linaro.org \
/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