linux-kernel - Re: Git next: Second stage of cpu

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Pine.LNX.4.64.0811060853320.3595@quilx.com>
Date:	Thu, 6 Nov 2008 08:54:21 -0600 (CST)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
cc:	Johannes Weiner <hannes@...xchg.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, travis@....com
Subject: Re: Git next: Second stage of cpu_alloc patches

On Thu, 6 Nov 2008, Stephen Rothwell wrote:

> On Thu, 6 Nov 2008 00:58:42 +0100 Johannes Weiner <hannes@...xchg.org> wrote:
> >
> > On Wed, Nov 05, 2008 at 07:54:39AM -0600, Christoph Lameter wrote:
> > > Ok so post a patchset to lkml and at the same time offer a git tree?
> >
> > Git is perhaps a more convenient way to pick up changesets compared to
> > extracting them from emails but review and discussion should still
> > happen by Email, no?
>
> Correct.

So what are the criteria when to repost a patchset? How extensive must the
changes be? This one has just minor fixes to the prior post.


--
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/