From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>,
Tom Tromey <tromey@redhat.com>, paawan oza <paawan1982@yahoo.com>
Subject: Re: [PATCH] arm reversible : progress <patch_1_phase_2>
Date: Thu, 03 Mar 2011 18:59:00 -0000 [thread overview]
Message-ID: <201103031859.44388.pedro@codesourcery.com> (raw)
In-Reply-To: <4D6FDFDB.5010706@vmware.com>
On Thursday 03 March 2011 18:37:15, Michael Snyder wrote:
> >>> diff -urN arm_new/arm-linux-tdep.c arm_orig/arm-linux-tdep.c
> >
> > The patch is reversed.
>
>
> Oza, you probably meant to say "-upN".
Nah, -r is to recurse in subdirectories, that was correct.
The problem is in the use of 'diff $NEW $OLD'. It should
be 'diff $OLD $NEW'.
But while at it, please do add the -p as Michael is suggesting.
It makes reading the patches easier.
Are you diffing two copies of the tree (one pristine, one
edited)? I suggest investing some time on learning to
work with some patch series management tool or process.
E.g., I work on top of a cvs checkout and manage my
patches with quilt; others use git, or stgit.
--
Pedro Alves
next prev parent reply other threads:[~2011-03-03 18:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 4:08 paawan oza
2011-03-03 18:32 ` Tom Tromey
2011-03-03 18:37 ` Michael Snyder
2011-03-03 18:59 ` Pedro Alves [this message]
2011-03-04 3:32 ` paawan oza
2011-03-04 3:56 ` paawan oza
2011-03-04 19:31 ` Tom Tromey
2011-03-04 20:09 ` Michael Snyder
2011-03-04 20:11 ` Tom Tromey
2011-04-10 9:41 ` [PATCH] arm reversible : progress <phase_2_complete> paawan oza
2011-04-11 3:05 ` Yao Qi
2011-04-11 4:52 ` paawan oza
2011-04-12 10:58 ` Yao Qi
2011-04-16 21:03 ` paawan oza
2011-04-20 19:16 ` [PATCH] arm reversible : <phase_2_complete> paawan oza
2011-04-21 20:55 ` Petr Hluzín
2011-04-22 5:49 ` paawan oza
2011-04-22 5:55 ` oza Pawandeep
2011-04-25 14:03 ` paawan oza
2011-05-01 1:20 ` Petr Hluzín
2011-05-02 14:47 ` Tom Tromey
2011-05-04 21:33 ` Petr Hluzín
2011-05-05 15:29 ` Tom Tromey
2011-05-07 13:50 ` paawan oza
2011-05-07 13:56 ` paawan oza
[not found] ` <172713.29831.qm__351.089161313389$1303740245$gmane$org@web112503.mail.gq1.yahoo.com>
2011-04-25 19:57 ` Tom Tromey
2011-04-28 18:26 ` paawan oza
2011-04-28 19:00 ` Tom Tromey
2011-04-28 19:22 ` paawan oza
[not found] ` <727567.12089.qm__13056.408687453$1304018591$gmane$org@web112511.mail.gq1.yahoo.com>
2011-04-28 19:36 ` Tom Tromey
2011-04-30 16:16 ` paawan oza
2011-05-02 13:28 ` Tom Tromey
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=201103031859.44388.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=paawan1982@yahoo.com \
--cc=tromey@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