| 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, 31 Mar 2009 17:30:06 +0200 From: "Hans-Peter Jansen" <hpj@...la.net> To: Arjan van de Ven <arjan@...ux.intel.com>, gitster@...ox.com Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Mike Galbraith <efault@....de>, Geert Uytterhoeven <Geert.Uytterhoeven@...ycom.com>, linux-kernel@...r.kernel.org Subject: Re: Linux 2.6.29 Am Dienstag, 31. März 2009 schrieb Arjan van de Ven: > Hans-Peter Jansen wrote: > > > > I always wonder, why Arjan does not intervene for his kerneloops.org > > project, since your approach opens a window of uncertainty during the > > merge window when simply using git as an efficient fetch tool. > > I would *love* it if Linus would, as first commit mark his tree as > "-git0" (as per snapshots) or "-rc0". So that I can split the "final" > versus "merge window" oopses. ..which is an important difference. I still vote for -pre for "preparation state" as -git0 does imply some sort of versioning, which *is* meaningless in this state. Linus, this would be a small step for you, but makes a big difference for those of us, that miss it sorely. Junio: is it possible to automate this in git somehow: make sure, that the first commit after a release really happens for a "new" version (e.g. a version patch to Makefile)? Pete -- 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