From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"Li, Xin" <xin.li@intel.com>
Subject: Re: [PATCH] Fix save.py bug
Date: Sat, 21 May 2011 07:29:23 -0400 [thread overview]
Message-ID: <32ADAEDD-EF15-4E24-95CE-30BDE8621D6D@cs.ubc.ca> (raw)
In-Reply-To: <BC00F5384FCFC9499AF06F92E8B78A9E2083B2F470@shsmsx502.ccr.corp.intel.com>
On 2011-05-20, at 11:30 PM, "Liu, Jinsong" <jinsong.liu@intel.com> wrote:
> Ian Jackson wrote:
>> Shriram Rajagopalan writes ("Re: [PATCH] Fix save.py bug"):
>>> Signed-off-by: Liu, Jinsong
>>> <jinsong.liu@intel.com<mailto:jinsong.liu@intel.com>> Acked-by: Ian
>>> Campbell
>>> <Ian.Campbell@eu.citrix.com<mailto:Ian.Campbell@eu.citrix.com>>
>>> Acked-by: Shriram Rajagopalan
>>> <rshriram@cs.ubc.ca<mailto:rshriram@cs.ubc.ca>>
>>
>> patching file tools/python/xen/remus/save.py
>> Hunk #1 FAILED at 161.
>> 1 out of 1 hunk FAILED -- saving rejects to file
>> tools/python/xen/remus/save.py.rej
>>
>> Ian.
>
> ?? some strange, I patched based on a recent tree :(
>
> Shriram, is there big change recently for save.py?
None at all!
> Anyway, I will pull latest xen tree next Monday and resend a patch to avoid hunk.
>
> Thanks,
> Jinsong
Shriram
next prev parent reply other threads:[~2011-05-21 11:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 8:30 [PATCH] Fix save.py bug Liu, Jinsong
2011-05-18 13:00 ` Shriram Rajagopalan
2011-05-19 12:05 ` Liu, Jinsong
2011-05-20 16:54 ` Ian Jackson
2011-05-21 3:30 ` Liu, Jinsong
2011-05-21 11:29 ` Shriram Rajagopalan [this message]
2011-05-23 8:22 ` Liu, Jinsong
2011-05-24 15:13 ` Ian Jackson
2011-05-25 2:32 ` Liu, Jinsong
-- strict thread matches above, loose matches on Subject: below --
2011-05-13 14:26 Liu, Jinsong
2011-05-13 14:36 ` Ian Campbell
2011-05-13 17:33 ` Liu, Jinsong
2011-05-17 1:58 ` Shriram Rajagopalan
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=32ADAEDD-EF15-4E24-95CE-30BDE8621D6D@cs.ubc.ca \
--to=rshriram@cs.ubc.ca \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jinsong.liu@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xin.li@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.