From: David Sterba <dsterba@suse.cz>
To: Timofey Titovets <nefelim4ag@gmail.com>
Cc: David Sterba <dsterba@suse.cz>,
Anand Jain <anand.jain@oracle.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] define BTRFS_DEV_STATE
Date: Wed, 13 Dec 2017 19:44:21 +0100 [thread overview]
Message-ID: <20171213184421.GE3553@twin.jikos.cz> (raw)
In-Reply-To: <CAGqmi77LeXmQCYVKC1wjHycOO12JTzRzcYreX0c2qN+LoEAKxA@mail.gmail.com>
On Wed, Dec 13, 2017 at 12:57:21PM +0300, Timofey Titovets wrote:
> > The kernel.org repository only gets the latest for-next, that is
> > assembled from the pending branches, and also after some testing. You
> > could still find 'misc-next' inside the for-next branch, but it's not
> > obvious.
> >
> > All the development branches are pushed to
> >
> > https://github.com/kdave/btrfs-devel or
> > http://repo.or.cz/linux-2.6/btrfs-unstable.git
> >
> > more frequently than the k.org/for-next is updated. I thought this has
> > become a common knowledge, but yet it's not documented on the wiki so.
> > Let's fix that.
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> Didn't know about your GitHub copy,
> may be that have sense to update:
> https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories
>
> And add new links? To:
> - k.org/for-next
> - https://github.com/kdave/btrfs-devel or
> - http://repo.or.cz/linux-2.6/btrfs-unstable.git
>
> Because current link to
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
> looks like a bit outdated.
Wiki updated, the section for kernel git repos was really out of date.
prev parent reply other threads:[~2017-12-13 18:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 9:15 [PATCH v3 0/5] define BTRFS_DEV_STATE Anand Jain
2017-12-10 9:15 ` [PATCH v3 1/5] btrfs: cleanup device states define BTRFS_DEV_STATE_WRITEABLE Anand Jain
2017-12-10 9:15 ` [PATCH v3 2/5] btrfs: cleanup device states define BTRFS_DEV_STATE_IN_FS_METADATA Anand Jain
2017-12-10 9:15 ` [PATCH v3 3/5] btrfs: cleanup device states define BTRFS_DEV_STATE_MISSING Anand Jain
2017-12-10 9:15 ` [PATCH v3 4/5] btrfs: cleanup device states define BTRFS_DEV_STATE_REPLACE_TGT Anand Jain
2017-12-10 9:15 ` [PATCH v3 5/5] btrfs: cleanup device states define BTRFS_DEV_STATE_FLUSH_SENT Anand Jain
2017-12-12 17:42 ` [PATCH v3 0/5] define BTRFS_DEV_STATE David Sterba
2017-12-12 22:38 ` Anand Jain
2017-12-13 2:26 ` David Sterba
2017-12-13 9:57 ` Timofey Titovets
2017-12-13 18:44 ` David Sterba [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=20171213184421.GE3553@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nefelim4ag@gmail.com \
/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.