From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Wiki update request: source repo page Was: [PATCH] Btrfs: use i_version instead of our own sequence
Date: Thu, 12 Apr 2012 21:41:17 +0000 (UTC) [thread overview]
Message-ID: <pan.2012.04.12.21.41.17@cox.net> (raw)
In-Reply-To: 20120412133107.GC1924@localhost.localdomain
Josef Bacik posted on Thu, 12 Apr 2012 09:31:07 -0400 as excerpted:
>> BTW.
>> 1. where is BTRFS devel git tree?
>> 2. when this is coming to mainline?
>>
>>
> There's a bunch, my personal tree with just my patches is here
>
> git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-work.git
>
> a tree with all outstanding mailinglist patches is here
>
> git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git
>
> and Chris's tree which is where all things go through to get to mainline
> is here
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
>
> It will probably be in the next merge window. Thanks,
Could this list be added to the btrfs wiki, source repositories page?
http://btrfs.ipv5.de/index.php?title=Btrfs_source_repositories
While there, please review the dkms information:
0) At least a paragraph actually describing what dkms is/does would be
extremely useful. A link to another page on the topic or to an external
dkms resource for more information is probably in order as well.
1) Near the top of the dkms section, under "You have a very recent
kernel", the for instance says dkms doesn't work with recent kernels, but
then backporting is mentioned. So you want to use it if you have a very
recent kernel, but it doesn't work with recent kernels and backporting is
needed? WTF?
2) Is Chris's tree STILL based on old 2.6.32 without further updates
except to btrfs? If so, the link to it in the earlier btrfs kernel
module git repository section should probably have a BIG WARNING TO THAT
EFFECT, instead of simply saying it downloads a complete Linux kernel
tree.
3) Further down there's a step that says Patch version script, noting
2.6.27, which is older still. Has cmason merged that patch?
4) The instructions appear to assume a kernel module an initr* based
setup. What about people who configure and build a custom monolithic
kernel, with module loading disabled?
--
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:[~2012-04-12 21:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 15:53 [PATCH] Btrfs: use i_version instead of our own sequence Josef Bacik
2012-04-12 13:22 ` Kasatkin, Dmitry
2012-04-12 13:31 ` Josef Bacik
2012-04-12 21:41 ` Duncan [this message]
2012-04-12 21:55 ` Wiki update request: source repo page Was: " Hugo Mills
2012-04-12 22:56 ` Duncan
2012-04-13 13:16 ` Hugo Mills
2012-04-13 18:48 ` Duncan
2012-04-13 20:03 ` cwillu
2012-04-13 21:55 ` Duncan
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.2012.04.12.21.41.17@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).