linux-kernel - lttng git.kernel.org tree

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-next>] [day] [month] [year] [list]

Message-ID: <20080619125157.GA14561@Krystal>
Date:	Thu, 19 Jun 2008 08:51:57 -0400
From:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: lttng git.kernel.org tree

Hi Peter,

I've been posting my LTTng work through patchsets for a while, but I
start to think it would be good to deploy a LTTng tree on
git.kernel.org, do you agree ?

Also, I guess I might have to do frequent rebases to follow mainline
because the LTTng patchset touches a lot of files (including the
low-level stuff, the architecture independant and arch. specific
instrumentation and the tracer itself). My current diffstat states :

 271 files changed, 10319 insertions(+), 674 deletions(-)

in 118 patches.

Is there some documentation that describes what would be the best way to
manage such a tree ? (frequent rebases or not ?)

Thanks,

Mathieu

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
--
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/