From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Change name from swiotlb-xen to xen-two tree and branches.
Date: Fri, 21 Jan 2011 11:45:01 -0500 [thread overview]
Message-ID: <20110121164501.GB29131@dumpdata.com> (raw)
Hey Stephen,
I was wondering if you would be OK change the name and branch
of one of my trees?
In the past the git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
was called 'swiotlb-xen' but it has expanded since I've took the role
of Xen co-maintainer.
Would you be OK changing the name from swiotlb-xen to 'xen-two' and
pulling from #linux-next branch instead of #master please?
I wonder if there is a better name than 'xen-two'?
next reply other threads:[~2011-01-21 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 16:45 Konrad Rzeszutek Wilk [this message]
2011-01-22 1:09 ` Change name from swiotlb-xen to xen-two tree and branches Stephen Rothwell
2011-01-22 9:34 ` Sedat Dilek
2011-01-22 22:48 ` Stephen Rothwell
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=20110121164501.GB29131@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).