From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jean Delvare <jdelvare@suse.de>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: failing to fetch the dmi tree
Date: Mon, 13 Jul 2020 09:11:02 +1000 [thread overview]
Message-ID: <20200713091102.28d186ca@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
Hi all,
Attempting to fetch the dmi tree gets this error:
http://jdelvare.nerim.net/devel/linux/jdelvare-dmi/series:
2020-07-13 08:58:05 ERROR 403: Forbidden.
I am still using the previously fetched quilt series.
Jean, I don't suppose you would like to produce a git tree for me to
fetch instead, as yours is the last quilt series I fetch (apart from
Andrew's which is special).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-07-12 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 23:11 Stephen Rothwell [this message]
2020-07-15 9:37 ` linux-next: failing to fetch the dmi tree Jean Delvare
2020-07-16 11:21 ` Jean Delvare
2020-07-16 12:55 ` 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=20200713091102.28d186ca@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jdelvare@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).