public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Lee Jones <lee.jones@linaro•org>
Cc: Samuel Ortiz <sameo@linux•intel.com>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: URL change for mfd tree?
Date: Thu, 31 Jul 2014 09:01:16 +1000	[thread overview]
Message-ID: <20140731090116.01e54d15@canb.auug.org.au> (raw)
In-Reply-To: <20140730071254.GC9030@lee--X1>

[-- Attachment #1: Type: text/plain, Size: 775 bytes --]

Hi Lee,

On Wed, 30 Jul 2014 08:12:54 +0100 Lee Jones <lee.jones@linaro•org> wrote:
>
> > I noticed commit 71e297b17bb6 ("MAINTAINERS: Update MFD repo location")
> > in the mfd-lj tree today.  In linux-next, I have the following mfd
> > trees:
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-fixes.git#master
> > git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-next.git#master
> > git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git#for-mfd-next
> > 
> > Does your commit mean that I should remove the first two?
> 
> Yes please.  They haven't been used for ~6 months and aren't likely to
> be used again.

I have removed them and renamed mfd-lj to mfd.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-07-30 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 23:24 linux-next: URL change for mfd tree? Stephen Rothwell
2014-07-30  7:12 ` Lee Jones
2014-07-30 23:01   ` Stephen Rothwell [this message]
2014-07-31  7:25     ` Lee Jones

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=20140731090116.01e54d15@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=lee.jones@linaro$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sameo@linux$(echo .)intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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