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
| ||
|
Date: Tue, 29 Jan 2008 22:41:24 +1100 (EST) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Matthew Wilcox <matthew@....cx> cc: linux-kernel@...r.kernel.org, Liam Howlett <howlett@...il.com>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: Pull request: TASK_KILLABLE On Mon, 28 Jan 2008, Matthew Wilcox wrote: > > I'd like you to pull the task_killable branch of > git://git.kernel.org/pub/scm/linux/kernel/git/willy/misc.git Well, Andrew already pointed out some of this, but I do want more information. There's a "git request-pull" script that even comes with git and that generates a shortlog, a proper url+branch description, and a diffstat of the changes. So that is already much more descriptive, but in addition to that, if this isn't one of the "regular" pulls (which it obviously isn't), I really want a human description too so that I know what I'm pulling and what it's all about. I do *not* want to be in the position of having to fetch first, just to be able to look at what I'm fetching. By the time I pull a branch, I want to basically know (a) what I'm pulling and (b) why I _want_ to pull it. 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/
Powered by blists - more mailing lists