From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Jacob Shin <jacob.shin@amd.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Xiantao Zhang <xiantao.zhang@intel.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 1/4] IOMMU: allow MSI message to IRTE propagation to fail
Date: Wed, 27 Mar 2013 10:45:30 -0400 [thread overview]
Message-ID: <5153060A.4000301@oracle.com> (raw)
In-Reply-To: <5152F14902000078000C8DAE@nat28.tlf.novell.com>
On 03/27/2013 08:16 AM, Jan Beulich wrote:
> I see your point, but I don't think using git for everything can be a
> requirement. I'm used to working with quilt, and have no plans of
> changing this, as I simply don't see any benefit in using git in my day
> to day coding work. I restrict uses of version control systems in
> general to the areas where they're needed - when working on
> shared repositories.
Not to make you change your mind about which revision control
package to use but I find guilt (http://linux.die.net/man/7/guilt) to
be a good quilt wrapper on top of git. For simple quilt operations
you only need to change one letter.
-boris
next prev parent reply other threads:[~2013-03-27 14:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 8:51 [PATCH 0/4] x86/IOMMU: multi-vector MSI prerequisites Jan Beulich
2013-03-26 9:03 ` [PATCH 1/4] IOMMU: allow MSI message to IRTE propagation to fail Jan Beulich
2013-03-27 11:45 ` George Dunlap
2013-03-27 12:16 ` Jan Beulich
2013-03-27 14:45 ` Boris Ostrovsky [this message]
2013-03-27 14:55 ` George Dunlap
2013-03-28 8:25 ` Jan Beulich
2013-03-28 9:46 ` Tim Deegan
2013-03-28 9:49 ` George Dunlap
2013-03-28 10:33 ` George Dunlap
2013-03-28 11:14 ` Jan Beulich
2013-03-28 11:25 ` Tim Deegan
2013-03-28 11:39 ` George Dunlap
2013-03-28 13:47 ` Stefano Stabellini
2013-05-06 20:25 ` Is: git send-email, patch sending, etc Was: " Konrad Rzeszutek Wilk
2013-05-07 8:53 ` Ian Campbell
2013-05-07 9:26 ` Wei Liu
2013-05-07 14:03 ` Konrad Rzeszutek Wilk
2013-03-27 17:26 ` George Dunlap
2013-03-28 8:27 ` Jan Beulich
2013-03-26 9:03 ` [PATCH 2/4] x86/MSI: cleanup to prepare for multi-vector MSI Jan Beulich
2013-03-26 9:04 ` [PATCH 3/4] AMD IOMMU: allocate IRTE entries instead of using a static mapping Jan Beulich
2013-04-02 8:38 ` [PATCH v2 " Jan Beulich
2013-04-11 0:34 ` Suravee Suthikulpanit
2013-03-26 9:05 ` [PATCH 4/4] AMD IOMMU: untie remap and vector maps Jan Beulich
2013-03-28 12:37 ` George Dunlap
2013-03-28 13:09 ` Jan Beulich
2013-03-28 13:40 ` George Dunlap
2013-03-29 5:18 ` [PATCH 0/4] x86/IOMMU: multi-vector MSI prerequisites Suravee Suthikulpanit
2013-03-29 5:45 ` Suravee Suthikulpanit
2013-04-02 8:39 ` Jan Beulich
2013-04-10 13:55 ` Jan Beulich
2013-04-10 14:38 ` Suravee Suthikulanit
2013-04-10 14:46 ` Jan Beulich
2013-04-11 1:51 ` Suravee Suthikulpanit
2013-04-11 7:13 ` Jan Beulich
2013-04-11 15:40 ` suravee suthikulpanit
2013-04-11 16:11 ` Jan Beulich
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=5153060A.4000301@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=jacob.shin@amd.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xen.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).