All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
	kvm-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org,
	"Luck, Tony" <tony.luck@intel.com>
Subject: Re: [kvm-devel] ia64 kernel patches?
Date: Fri, 25 Jan 2008 15:11:42 +0000	[thread overview]
Message-ID: <4799FC2E.7040207@sgi.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDCCE7371@pdsmsx415.ccr.corp.intel.com>

Zhang, Xiantao wrote:
> Jes Sorensen wrote:
>> Hi Xiantao,
>>
>> If you could put up the patches somewhere, I could
>> help you clean them up and push them. I would prefer not
>> to wait until they appear in Linus' tree if possible.
> 
> Hi, Jes
> 	You don't need to wait so long. We will push it to Avi's tree first in near future once ia64 kernel ready. 
> Thanks
> Xiantao

Hi Xiantao,

Please, put it in a public tree somewhere, either on kernel.org or
a different public server. This is how everybody else does Open Source
development - it is much easier in the long run as others will be
able to send you fixes instead of waiting 4 months.

Thanks,
Jes

WARNING: multiple messages have this Message-ID (diff)
From: Jes Sorensen <jes@sgi.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
	kvm-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org,
	"Luck, Tony" <tony.luck@intel.com>
Subject: Re: [kvm-devel] ia64 kernel patches?
Date: Fri, 25 Jan 2008 16:11:42 +0100	[thread overview]
Message-ID: <4799FC2E.7040207@sgi.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDCCE7371@pdsmsx415.ccr.corp.intel.com>

Zhang, Xiantao wrote:
> Jes Sorensen wrote:
>> Hi Xiantao,
>>
>> If you could put up the patches somewhere, I could
>> help you clean them up and push them. I would prefer not
>> to wait until they appear in Linus' tree if possible.
> 
> Hi, Jes
> 	You don't need to wait so long. We will push it to Avi's tree first in near future once ia64 kernel ready. 
> Thanks
> Xiantao

Hi Xiantao,

Please, put it in a public tree somewhere, either on kernel.org or
a different public server. This is how everybody else does Open Source
development - it is much easier in the long run as others will be
able to send you fixes instead of waiting 4 months.

Thanks,
Jes

  reply	other threads:[~2008-01-25 15:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 16:56 ia64 kernel patches? Jes Sorensen
     [not found] ` <4798C34F.9010509-sJ/iWh9BUns@public.gmane.org>
2008-01-24 18:53   ` Chris Wright
2008-01-25  1:18     ` [kvm-devel] " Zhang, Xiantao
2008-01-25  1:18       ` Zhang, Xiantao
     [not found]       ` <42DFA526FC41B1429CE7279EF83C6BDCCE708C-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-25  8:39         ` Jes Sorensen
2008-01-25  8:39           ` Jes Sorensen
2008-01-25 10:50           ` [kvm-devel] " Zhang, Xiantao
2008-01-25 10:50             ` Zhang, Xiantao
2008-01-25 15:11             ` Jes Sorensen [this message]
2008-01-25 15:11               ` Jes Sorensen
2008-01-26  4:56               ` Zhang, Xiantao
2008-01-26  4:56                 ` Zhang, Xiantao

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=4799FC2E.7040207@sgi.com \
    --to=jes@sgi.com \
    --cc=chrisw@sous-sol.org \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-ia64@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=xiantao.zhang@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.