From: Artem Bityutskiy <dedekind1@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Brian Norris <computersforpeace@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Vincenzo Aliberti <vincenzo.aliberti@gmail.com>
Subject: Re: linux-next: build failure after merge of the l2-mtd tree
Date: Tue, 27 May 2014 13:40:03 +0300 [thread overview]
Message-ID: <1401187203.1304.125.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20140527095942.0a071e63@canb.auug.org.au>
On Tue, 2014-05-27 at 09:59 +1000, Stephen Rothwell wrote:
> Hi Brian,
>
> On Mon, 26 May 2014 10:42:25 -0700 Brian Norris <computersforpeace@gmail.com> wrote:
> >
> > On Thu, May 22, 2014 at 03:30:47PM +1000, Stephen Rothwell wrote:
> > > Hi Artem,
> >
> > FYI, I'm managing this tree now, not Artem.
>
> OK, noted. Is there a different URL for the tree as well? Currently
> it is git://git.infradead.org/users/dedekind/l2-mtd-2.6.git#master .
Hi Stephen,
apologies for not informing you about the onwership changes in time. But
yes, Brian takes care of this tree now.
The URL you have is technically correct, but it is better to use this
instead:
git://git.infradead.org/l2-mtd.git#master
The old URL is just a symlink to the above one nowadays. Thanks!
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2014-05-27 10:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 5:30 linux-next: build failure after merge of the l2-mtd tree Stephen Rothwell
2014-05-26 17:42 ` Brian Norris
2014-05-26 23:59 ` Stephen Rothwell
2014-05-27 10:40 ` Artem Bityutskiy [this message]
2014-05-27 22:49 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2017-08-28 2:19 Stephen Rothwell
2017-08-28 22:06 ` Brian Norris
2017-02-09 1:08 Stephen Rothwell
2017-02-09 1:59 ` Brian Norris
2016-07-19 0:59 Stephen Rothwell
2016-07-19 1:20 ` Brian Norris
2016-07-19 1:46 ` Stephen Rothwell
2015-12-21 5:47 Stephen Rothwell
2015-09-30 5:16 Stephen Rothwell
2012-10-12 0:14 Stephen Rothwell
2012-10-12 4:51 ` Dinh Nguyen
2012-10-18 0:28 ` Stephen Rothwell
2012-10-18 9:26 ` Artem Bityutskiy
2012-02-07 2:58 Stephen Rothwell
2012-02-07 8:02 ` Artem Bityutskiy
2012-02-06 1:07 Stephen Rothwell
2012-02-06 9:14 ` Artem Bityutskiy
2012-02-06 21:10 ` Stephen Rothwell
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=1401187203.1304.125.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vincenzo.aliberti@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 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).