linux-kernel - Re: linux-next: Tree for December 14 (New tree: vfs-scale)

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: <20101214223339.5bf5db49.sfr@canb.auug.org.au>
Date:	Tue, 14 Dec 2010 22:33:39 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	sedat.dilek@...il.com
Cc:	Sedat Dilek <sedat.dilek@...glemail.com>,
	Nick Piggin <npiggin@...nel.dk>,
	Nick Kossifidis <mickflemm@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Peter Hutterer <peter.hutterer@...-t.net>
Subject: Re: linux-next: Tree for December 14 (New tree: vfs-scale)

Hi Sedat,

On Tue, 14 Dec 2010 10:38:35 +0100 Sedat Dilek <sedat.dilek@...glemail.com> wrote:
>
> [ QUOTE ]
> Hi all,
> 
> [The mirroring on kernel.org is being slow again ...]
> 
> Changes since 20101213:
> 
> New tree: vfs-scale
> 
> The vfs-scale tree gained a conflict against the fuse tree.
> 
> The ieee1394 tree lost its build failure.
> 
> The wireless tree gained conflicts against the wireless-current tree.
> 
> The sound tree lost its conflict.
> 
> The input tree gained a conflict against Linus' tree.
> 
> The voltage tree gained a build failure so I used the version from
> next-20101213.
> 
> The swiotlb-xen tree lost its build failure.
> 
> The cleancache tree gained a conflict against the vfs-scale tree.
> [ /QUOTE ]
> 
> First of all congrats to all involved parties so that the work of Nick
> was accepted as "vfs-scale" into linux-next!

The "Nick" associated with the vfs-scale tree is Nick Piggin (cc'd).

> I played yesterday with the new refreshed patchset (manually merged
> and fixed) against systemd-v15 with kgdb/kdb.
> Oh yes, there is a "dmesg" command :-) and with "btp $pid" I yesterday
> night saw a NULL dereference in the backtrace.
> Currently, I am compiling linux-next (next-20101214) and will take
> some pictures with my digicam.
> 
> Some recommends (not that I want to teach you as GIT is for me new
> playground and I follow mostly the commit-messages, which not means I
> understand the complexity of the patchset), but ...
> 
> 1. Please give commits a proper/sane "commit subject"
> "Build fix" or "Fixed build failure" is not saying much.
> 
> 2. Add credits for people investing time to test and report
> Same commits did not have also credits for people reporting the build failures.
> A reference to LKML posting would be fine in the "commit-body" (sorry
> for my comparison with Email, do not know the GIT term).
> 
> This all is not to punish you, it is for following and documenting the
> whole process.
> 
> Peter Hutterer has a wonderful blog article "On commit messages"
> concerning this topic.
> If all of us would follow them, the working-together will be more fruitful.
> 
> My 0.02EUR.
> 
> - Sedat -
> 
> [1] http://who-t.blogspot.com/2009/12/on-commit-messages.html

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped