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: <20060927205428.c969984e.kernel1@cyberdogtech.com>
Date:	Wed, 27 Sep 2006 20:54:28 -0400
From:	Matt LaPlante <kernel1@...erdogtech.com>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How long to wait on patches?

On Wed, 27 Sep 2006 01:45:05 +0200
Adrian Bunk <bunk@...sta.de> wrote:

> On Mon, Sep 25, 2006 at 10:52:12AM -0400, Matt LaPlante wrote:
> 
> > 2.6.18 is out, so I feel the urge to revive a dead topic. :) Any idea when we might get my ancient trivials included in the new gits?  I'm still lurking around and ready to do more pointless doc-checking tasks, but I really want the old stuff merged so I can rebase around it.
> >...
> 
> During the 2 weeks until 2.6.19-rc1.
> 
> It wouldn't be good if I'd forward all the trivial patches today 
> probably breaking the context for pending merges.

Alright, good to know.  If I may suggest:

99% of my changes are to text Docs, not source.  I don't believe we would be risking code breakage as a result of merging them.  In this case of course I don't expect you to root through the trivial box and pull out my patches, but maybe this isn't the best way for me to submit them in the first place?  It seems like a particularly small and unnecessary window for somebody to update text files in.  Is there a different tree or maintainer that would be better suited for this type of thing?

Thanks again.

-
Matt

> 
> cu
> Adrian
> 


-
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