All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Quigley <jquigley@jquigley.com>
To: Project Hail <hail-devel@vger.kernel.org>
Subject: Re: Interested in contributing
Date: Thu, 17 Sep 2009 23:36:34 -0500	[thread overview]
Message-ID: <4AB30E52.3090601@jquigley.com> (raw)
In-Reply-To: <4AB30DF2.6010200@jquigley.com>

John Quigley wrote:
> Jeff Garzik wrote:
>> The only other, minor detail I would add is to practice building from
>> the git repository.  These projects are definitely in the "heavy
>> development" phase, and problems with release tarballs may have
>> already been fixed in the git repo by the time someone gets around to
>> reporting the bug.
> 
> I'm doing all of my work, include build/test from your git repos; I'm 
> also building on Debian (testing), which I gather differs from your 
> folks' development environments (RH-based?).
> 
> I have some (simple) libtool patches to your build system that allow for 
> Debian-based builds, given the more recent libtool packages.  I assume 
> you'd want any and all such patches?

For that matter, what is your development environment?  I should 
probably try to duplicate that on my end (if only in a vm) for testing 
purposes.

I'm also going to try documenting some of these environment- and 
build-related matters on the wiki.

- John Quigley

  reply	other threads:[~2009-09-18  4:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26  1:13 Interested in contributing John Quigley
2009-08-26  1:52 ` Pete Zaitcev
2009-08-26  3:19   ` John Quigley
2009-08-26 16:44 ` Jeff Garzik
2009-09-18  4:34   ` John Quigley
2009-09-18  4:36     ` John Quigley [this message]
2009-09-18  4:49       ` John Quigley
2009-09-18  5:13         ` John Quigley
2009-09-18 11:22         ` Jeff Garzik
2009-09-18 14:30           ` John Quigley
2009-09-18 11:21     ` Jeff Garzik
2009-09-18 18:59       ` Pete Zaitcev

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=4AB30E52.3090601@jquigley.com \
    --to=jquigley@jquigley.com \
    --cc=hail-devel@vger.kernel.org \
    /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.