From: Zheng Liu <gnehzuil.liu@gmail.com>
To: jon ernst <jonernst07@gmx.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: dev branch or master branch?
Date: Sat, 1 Jun 2013 01:13:52 +0800 [thread overview]
Message-ID: <20130531171352.GA6915@gmail.com> (raw)
In-Reply-To: <20130531163305.297890@gmx.com>
On Fri, May 31, 2013 at 12:33:05PM -0400, jon ernst wrote:
> Hi list,
>
> Patches that people send to this list, are those against to dev branch or master branch?
You'd better send a patch that bases against dev branch. You can clone
ext4 tree from here:
https://git.kernel.org/cgit/linux/kernel/git/tytso/ext4.git/
Regards,
- Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-05-31 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 16:33 dev branch or master branch? jon ernst
2013-05-31 17:13 ` Zheng Liu [this message]
2013-05-31 23:07 ` Theodore Ts'o
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=20130531171352.GA6915@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=jonernst07@gmx.com \
--cc=linux-ext4@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).