From: Jean Delvare <jdelvare@suse.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Mark Brown <broonie@kernel.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: linux-next: jdelvare-hwmon tree unfetchable
Date: Tue, 2 Sep 2014 09:54:55 +0200 [thread overview]
Message-ID: <20140902095455.77a91b40@endymion.delvare> (raw)
In-Reply-To: <54049590.6060500@roeck-us.net>
Hi all,
On Mon, 01 Sep 2014 08:49:36 -0700, Guenter Roeck wrote:
> On 09/01/2014 05:28 AM, Mark Brown wrote:
> > Today's linux-next merge of the jdelvare-hwmon tree got a conflict with Linus'
> > tree which appeared to be due to the hwmon quilt series I got from Stephen being
> > based on v3.14-rc3 and subsequent changes from mainline interacting badly with
> > it. In addition I'm not able to check the original series since linux-fr.org does
> > not resolve for me.
>
> Jean dropped the linux-fr.org domain, and his old e-mail address probably
> won't work anymore.
I can confirm that. linux-fr.org is history, from now on I'll be using
my @suse.de address for all open source related work. I thought I had
already updated all references and let everyone involved know about the
change, but apparently I failed to do so, sorry about that.
> The alternate (and temporary) pointer he gave me
> is http://jdelvare.nerim.net/devel/linux-3/jdelvare-hwmon/. It is empty,
> so you did not miss anything.
That's right. As many temporary things, I'm afraid it's there to
last ;-)
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2014-09-02 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 12:28 linux-next: jdelvare-hwmon tree unfetchable Mark Brown
2014-09-01 13:18 ` Fabio Estevam
2014-09-01 13:46 ` Mark Brown
2014-09-01 15:49 ` Guenter Roeck
2014-09-01 15:53 ` Mark Brown
2014-09-02 7:54 ` Jean Delvare [this message]
2014-09-08 0:55 ` Stephen Rothwell
2014-09-01 16:57 ` Geert Uytterhoeven
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=20140902095455.77a91b40@endymion.delvare \
--to=jdelvare@suse.de \
--cc=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).