linux-kernel - Re: [GIT PULL] kvm oops fix

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.0.98.0704190949580.9964@woody.linux-foundation.org>
Date:	Thu, 19 Apr 2007 09:53:00 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Avi Kivity <avi@...ranet.com>
cc:	linux-kernel@...r.kernel.org, kvm-devel@...ts.sourceforge.net
Subject: Re: [GIT PULL] kvm oops fix

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/