Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: paawan oza <paawan1982@yahoo.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: final   i386.floating.record.patch
Date: Thu, 30 Jul 2009 18:00:00 -0000	[thread overview]
Message-ID: <266448.98713.qm@web112520.mail.gq1.yahoo.com> (raw)
In-Reply-To: <4A70EA5C.3090702@vmware.com>


Hi,

please find my answers below.

 1) Are you using a Windows machine to send your
 emails?  If so,
 is it possible that there is a Unix/Linux machine you could
 try
 sending from?  Your attachments look OK for me, but
 some people
 seem to have had problems with them.

Oza : I used to send all from windows till now.
but this patch I sent it from Linux...from opera.
 
 2) And are you using cut-and-paste to insert the patches
 into the
 body of your email?  That would certainly cause
 problems, because
 tabs might be changed into spaces (which is exactly what
 was
 causing patch to fail for me today).
 
Oza: yes I am using copy-paste....I dont know any-other way.
because attachmenet are not welcome, so I am not sure how I could proceed with this.

I will send you updated patch.....may be I might have mistaken of old gdb file. sorry for incovenience.

Regards,
Oza.





 
> 

--- On Thu, 7/30/09, Michael Snyder <msnyder@vmware.com> wrote:

> From: Michael Snyder <msnyder@vmware.com>
> Subject: Re: final   i386.floating.record.patch
> To: "paawan oza" <paawan1982@yahoo.com>
> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> Date: Thursday, July 30, 2009, 6:03 AM
> Michael Snyder wrote:
> > paawan oza wrote:
> >> Hi All,
> >>
> >> Now the format is modified, and I am submitting
> the patch, I hope this meets the expectations.
> >> thank you all for your review comments specially
> Micahel and Hui.
> >> please find the patch as follows.
> > 
> > I'm sorry, Oza, but the patch does not apply.
> > 
> > bash-3.00$ patch <
> ~/oza3/i386.floating.record.patch.txt
> > patching file i386-tdep.c
> > Hunk #3 succeeded at 4249 with fuzz 1.
> > Hunk #4 FAILED at 4263.
> > Hunk #5 FAILED at 4321.
> > Hunk #6 FAILED at 4330.
> > Hunk #7 FAILED at 4351.
> > Hunk #8 FAILED at 4362.
> > Hunk #9 FAILED at 4414.
> > Hunk #10 FAILED at 4451.
> > Hunk #11 FAILED at 4470.
> > Hunk #12 FAILED at 4489.
> > Hunk #13 FAILED at 5110.
> > 10 out of 13 hunks FAILED -- saving rejects to file
> i386-tdep.c.rej
> 
> Just thinking about it -- this was the first time that I
> had
> trouble applying one of your patches.  But I
> remembered that
> previously, I always applied your patch from the
> attachment.
> This time there was no attachment, so I saved the email
> message
> and edited out the email headers.
> 
> I know you've had a lot of trouble with attachments and
> patches
> not applying -- I'd like to get it sorted out if possible.
> 
 1) Are you using a Windows machine to send your
 emails?  If so,
 is it possible that there is a Unix/Linux machine you could
 try
 sending from?  Your attachments look OK for me, but
 some people
 seem to have had problems with them.
 
 2) And are you using cut-and-paste to insert the patches
 into the
 body of your email?  That would certainly cause
 problems, because
 tabs might be changed into spaces (which is exactly what
 was
 causing patch to fail for me today).
 
 
> 




  reply	other threads:[~2009-07-30 16:54 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-26 14:27 i386.record.floating.point.patch : with more testing and assurity paawan oza
2009-07-26 22:51 ` Michael Snyder
2009-07-27  1:09 ` Michael Snyder
2009-07-29 18:30   ` final i386.floating.record.patch paawan oza
2009-07-29 22:01     ` Michael Snyder
2009-07-30  0:44       ` Michael Snyder
2009-07-30 18:00         ` paawan oza [this message]
2009-07-30 21:13           ` Michael Snyder
2009-07-27  2:33 ` i386.record.floating.point.patch : with more testing and assurity Samuel Bronson
2009-07-29 18:34 final i386.floating.record.patch paawan oza
2009-07-30  6:24 ` Michael Snyder
2009-07-30 18:09   ` paawan oza
2009-08-03 14:59   ` paawan oza
2009-08-03 20:07     ` Michael Snyder
2009-08-03 14:56 paawan oza
2009-08-03 20:04 ` Michael Snyder
2009-08-04  3:20 ` Hui Zhu
2009-08-04 13:03   ` paawan oza
2009-08-04 13:06 paawan oza
2009-08-04 13:58 ` Hui Zhu
2009-08-04 14:18   ` paawan oza
2009-08-04 14:26   ` paawan oza
2009-08-04 14:43     ` Hui Zhu
2009-08-04 17:59       ` paawan oza
2009-08-05  1:29         ` Hui Zhu
2009-08-05  1:34         ` Michael Snyder
2009-08-05 13:48           ` paawan oza
2009-08-07  7:25 paawan oza
2009-08-07 15:50 ` Hui Zhu
2009-08-16 21:41 ` Michael Snyder
2009-08-17  9:17   ` Hui Zhu
2009-08-17 16:16     ` paawan oza
2009-08-18 15:22 paawan oza
2009-08-19  2:17 ` Hui Zhu
2009-08-19  2:44   ` Hui Zhu
2009-08-21 16:59 paawan oza
2009-08-23  1:32 ` Hui Zhu
2009-08-23  3:00   ` Michael Snyder
2009-08-23  9:04     ` paawan oza
2009-08-23  9:29     ` paawan oza
2009-09-09  0:19 ` Michael Snyder
2009-09-10  1:13   ` paawan oza
2009-09-26  9:33   ` paawan oza
2009-12-10  7:55 ` Hui Zhu

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=266448.98713.qm@web112520.mail.gq1.yahoo.com \
    --to=paawan1982@yahoo.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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