From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: lttng git.kernel.org tree
Date: Thu, 19 Jun 2008 08:51:57 -0400 [thread overview]
Message-ID: <20080619125157.GA14561@Krystal> (raw)
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
next reply other threads:[~2008-06-19 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 12:51 Mathieu Desnoyers [this message]
2008-06-19 17:03 ` lttng git.kernel.org tree Josh Boyer
2008-06-19 17:52 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080619125157.GA14561@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.