lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 1 Sep 2014 18:57:29 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Mark Brown <broonie@...nel.org>, Jean Delvare <jdelvare@...e.de>
Cc:	Jean Delvare <khali@...ux-fr.org>,
	Linux-Next <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Guenter Roeck <linux@...ck-us.net>
Subject: Re: linux-next: jdelvare-hwmon tree unfetchable

CC jean @ suse

On Mon, Sep 1, 2014 at 2:28 PM, Mark Brown <broonie@...nel.org> 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.

Same here. The domain exists, and seems to have been updated yesterday,
possibly breaking it?

> I'm really confused by what's going on here so I skipped the tree for today.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists