From: Erik Andersen <andersen@codepoet.org>
To: buildroot@busybox.net
Subject: [Buildroot] contrib packages
Date: Thu, 10 Aug 2006 11:57:49 -0600 [thread overview]
Message-ID: <20060810175749.GB20615@codepoet.org> (raw)
In-Reply-To: <DDB043F5-416D-4062-AF58-A6295D132D95@cs.auckland.ac.nz>
On Thu Aug 10, 2006 at 03:13:36PM +1200, Robert Carter wrote:
> I've managed to add a new package to buildroot for ntfsprogs. I've
> still got some testing to do but I was wondering what is the right
> way to make my additions available for other developers to use?
>
> Is a diff of the modified files posted here appropriate or should I
> be using svn?
Best is to submit a diff (diff -u) vs buildroot and post your
patch to the bug tracking system. That ensures your patch wont
get lost. Then, one of the committers (such as myself) will
sometime get around to reviewing your patch and apply it.
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
prev parent reply other threads:[~2006-08-10 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 3:13 [Buildroot] contrib packages Robert Carter
2006-08-10 17:57 ` Erik Andersen [this message]
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=20060810175749.GB20615@codepoet.org \
--to=andersen@codepoet.org \
--cc=buildroot@busybox.net \
/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