From: Linus Torvalds <torvalds@linux-foundation.org>
To: Avi Kivity <avi@qumranet.com>
Cc: linux-kernel@vger.kernel.org, kvm-devel@lists.sourceforge.net
Subject: Re: [GIT PULL] kvm oops fix
Date: Thu, 19 Apr 2007 09:53:00 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0704190949580.9964@woody.linux-foundation.org> (raw)
In-Reply-To: <1176997839110-git-send-email-avi@qumranet.com>
On Thu, 19 Apr 2007, Avi Kivity wrote:
>
> Please pull from the 'linus' branch of
>
> git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
*please* put the branch-name after the git repo, so that I can
cut-and-paste without noticing only afterwards that the diffstat doesn't
match what it was supposed to, and I got the wrong commits, and have to
undo and re-do the pull..
Yeah, I didn't do that mistake this time, and in fact, I seldom do, but
every time the branch is mentioned somewhere else than with the actual
repo to pull, I get nervous.
So I've said this a million times before, but I'll say it one more
time: if it's not the main branch, the message should be
Please pull from the 'linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git linus
to get the following changes: ...
so that when I cut-and-paste the URL (you didn't think I'd try to type it
in by hand, did you?) I get the branch automatically.
Linus
next prev parent reply other threads:[~2007-04-19 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 15:50 Avi Kivity
2007-04-19 16:53 ` Linus Torvalds [this message]
2007-04-19 19:09 ` Jeff Garzik
2007-04-19 19:24 ` [kvm-devel] " David Brown
2007-04-19 19:34 ` Jeff Garzik
2007-04-19 19:40 ` J. Bruce Fields
2007-04-19 20:30 ` Linus Torvalds
2007-04-19 22:59 ` Linus Torvalds
2007-04-20 4:54 ` [kvm-devel] " David Brown
2007-04-22 5:52 ` Avi Kivity
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=alpine.LFD.0.98.0704190949580.9964@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®