From: Christoffer Dall <christoffer.dall@linaro.org>
To: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Rebaseing kvm-arm-next
Date: Wed, 26 Jun 2013 11:57:39 -0700 [thread overview]
Message-ID: <20130626185739.GA41132@lvm> (raw)
Hi all,
I messed up my workflow earlier on, so I had to rebase kvm-arm-next onto
kvm/next. I will do everything in my powers to avoid this in the
future.
Sorry for any troubles.
-Christoffer
reply other threads:[~2013-06-26 18:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130626185739.GA41132@lvm \
--to=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-next@vger.kernel.org \
/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