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] [day] [month] [year] [list]
Date:	Fri, 21 Jul 2006 18:45:23 -0700
From:	Andrew Morton <akpm@...l.org>
To:	David Lang <dlang@...italinsight.com>
Cc:	kernel1@...erdogtech.com, linux-kernel@...r.kernel.org
Subject: Re: How long to wait on patches?

On Fri, 21 Jul 2006 15:45:08 -0700 (PDT)
David Lang <dlang@...italinsight.com> wrote:

> > I checked the FAQ but didn't see an answer to this.  Over the past few weeks 
> > I've submitted probably around 8 simple typo-fix patches all of which seemed 
> > to be approved by others on the list.  I've been following the GIT, but these 
> > patches haven't been merged yet.  I know people are busy with other things, 
> > probably more important, but I would like to know how long is "acceptable" to 
> > wait before I should re-submit a patch.  Obviously if enough time passes, 
> > patches start to break as source files change.  I don't mean to be a nuisance; 
> > I'm just trying to determine proper protocol.  That and the fact I can submit 
> > several more patches once I get some of these old ones out of my queue. :)
> 
> be sure to watch the -mm tree as well, a lot of patches are picked up by Andrew 
> to be fed to Linus that way

Yes, I hoover up unloved patches from the mailing list.  But only from this
mailing list, and there are probably lots of potentially-useful patches on
other lists which get lost.

However I have a personal i-dont-do-typo-patches policy.  Resending them to
kernel-janitor-discuss@...ts.sourceforge.net would be a good idea.
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ