From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [Question]: Contributing to btrfs
Date: Sun, 21 Feb 2016 06:14:27 +0000 (UTC) [thread overview]
Message-ID: <pan$10f61$d1f2f571$e6679adf$76c72183@cox.net> (raw)
In-Reply-To: 20160220224050.GA10864@carbon.home
Philippe Loctaux posted on Sat, 20 Feb 2016 23:40:50 +0100 as excerpted:
> I'm new to the mailing list and btrfs in general (I've been using it for
> two weeks on my new arch install) and I'd like to contribute to the code
> :)
>
> I know how to work w/ git and patches, I just wanted to know which git
> repo I need to clone to start contributing :)
>
> I went on the kernel wiki and I saw some git repos, that confused me,
> that's why I'm asking here :)
You mention the kernel wiki, but don't mention the btrfs wiki, which is
on a kernel wiki subdomain, and which has the btrfs-specific information,
both for users and for developers. Missing that is thus likely to be the
source of your confusion, which makes it easy to fix. =:^)
https://btrfs.wiki.kernel.org
More specifically of interest for developers:
https://btrfs.wiki.kernel.org/index.php/Main_Page#Developer_documentation
But as you're a new user as well, and missed the btrfs user docs on the
wiki, spend some time looking over them as well, as they'll almost
certainly contain some rather useful user information you missed, as well.
If OTOH, you meant that you read that, and were still confused, as may be
the case give that I too was a bit confused as a list regular, when I was
looking for actual development sources, as the kernel.org userspace repo
only contains releases, the repo.or.cz repo is what I was looking for to
get the actual under development userspace HEAD code. Or just do what I
did and browse around a bit until you figure out which of the listed repos
you're actually after. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-02-21 18:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 21:09 [Question]: Contributing to btrfs Philippe Loctaux
2016-02-20 22:40 ` Philippe Loctaux
2016-02-21 6:14 ` Duncan [this message]
2016-02-22 1:18 ` Qu Wenruo
2016-02-22 7:26 ` Philippe Loctaux
2016-02-22 7:34 ` Qu Wenruo
2016-02-22 7:42 ` Philippe Loctaux
2016-02-22 10:47 ` Filipe Manana
2016-02-22 12:02 ` Simon Quigley
2016-02-22 13:29 ` Filipe Manana
2016-02-22 14:45 ` Simon Quigley
2016-02-23 1:32 ` Qu Wenruo
2016-02-23 2:07 ` Simon Quigley
2016-02-23 2:20 ` Qu Wenruo
2016-02-22 16:45 ` Philippe Loctaux
2016-02-22 12:18 ` David Sterba
2016-02-22 16:41 ` Philippe Loctaux
2016-02-22 17:15 ` David Sterba
2016-02-22 11:34 ` David Sterba
2016-02-22 16:38 ` Philippe Loctaux
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='pan$10f61$d1f2f571$e6679adf$76c72183@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).