From: Randy Dunlap <rdunlap@infradead.org>
To: Chen Gang <gang.chen@asianux.com>, linux-next@vger.kernel.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Consult] About linux-next branches
Date: Mon, 14 Oct 2013 19:50:51 -0700 [thread overview]
Message-ID: <525CAD8B.2090809@infradead.org> (raw)
In-Reply-To: <525CA928.8000909@asianux.com>
On 10/14/13 19:32, Chen Gang wrote:
> Hello All:
>
> I am developing with linux-next tree which have multiple branches.
>
> Now I use "git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git"
> which is not updated within 2 weeks. But it seems other linux-next
> branches continue updating.
>
> So need I choose another linux-next tree for developing?
>
>
> Welcome any members' suggestions or completions.
>
> Thanks.
>
The git location is announced in each day's linux-next announcement email.
E.g. (while Stephen Rothwell is taking a break):
<quote>
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131014 tag is also provided for convenience.
</quote>
--
~Randy
next prev parent reply other threads:[~2013-10-15 2:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 2:32 [Consult] About linux-next branches Chen Gang
2013-10-15 2:50 ` Randy Dunlap [this message]
2013-10-15 4:11 ` Chen Gang
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=525CAD8B.2090809@infradead.org \
--to=rdunlap@infradead.org \
--cc=gang.chen@asianux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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