From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: Noah Watkins <nwatkins@ittc.ku.edu>
Cc: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] Re: git/svn development process
Date: Thu, 26 Jul 2007 11:38:17 +0200 [thread overview]
Message-ID: <20070726093817.GA4842@mail.linbit.com> (raw)
In-Reply-To: <20070725224946.GA3373@ittc.ku.edu>
On Wed, Jul 25, 2007 at 05:49:46PM -0500, Noah Watkins wrote:
> I was interested in your development process now that you have expressed
> an interest in pushing your code into mainline. Should people wanting to
> contribute be working off of the SVN trunk, or the GIT tree which was
> posted on LKML?
so, I guess, you have something specific in mind
that you would like to contribute?
for small things right now, it would be ok to
base it on svn, and probably easier on the contributors side,
because I guess, even though few if any feature changes are expected,
the source layout of the git tree will change a lot before inclusion,
causing your patches to not apply.
for me, it would of course be nice if you'd do the extra work to
make your patches apply, and submit against the git tree.
to make things easier on both ends,
I try to fold back any changes neccessary for kernel.org inclusion
onto the drbd/branches/drbd-8.1 branch.
any future development will likely be based on that branch,
read this will become drbd "trunk" soonish.
so for now, as a potential contributor to drbd,
your best way to proceed is to base your work on that svn brach.
it has the same "problem" now, that I expect the source code layout to
change a lot, still, though most whitespace fixes have been done
already. it has the additional benefit over the git repository, that
there we will keeps backwards compatibility with older kernels
(back to the 2.6.5 derived SLES9, or 2.6.9 derived RHEL 4).
thanks,
--
: Lars Ellenberg Tel +43-1-8178292-0 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe http://www.linbit.com :
parent reply other threads:[~2007-07-26 9:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20070725224946.GA3373@ittc.ku.edu>]
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=20070726093817.GA4842@mail.linbit.com \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.com \
--cc=nwatkins@ittc.ku.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox