From: "sfr@canb.auug.org.au via RT" <kernel-helpdesk@rt.linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
rdunlap@infradead.org
Subject: Re: [Kernel.org Helpdesk #7062] AutoReply: Re: linux-next: Tree for Sep 12
Date: Sat, 13 Sep 2014 02:08:58 +0000 [thread overview]
Message-ID: <rt-3.8.13-21021-1410574137-1910.7062-6-0@linuxfoundation.org> (raw)
In-Reply-To: <20140913120848.243db589@canb.auug.org.au>
[-- Attachment #1.1: Type: text/plain, Size: 1808 bytes --]
Hi,
On Sat, 13 Sep 2014 02:00:02 +0000 "Kernel.org IT Helpdesk via RT" <kernel-helpdesk@rt.linuxfoundation.org> wrote:
>
>
> Greetings,
>
> Your support ticket regarding:
> "Re: linux-next: Tree for Sep 12",
> has been entered in our ticket tracker. A summary of your ticket appears below.
>
> If you have any follow-up related to this issue, please reply to this email or include:
>
> [Kernel.org Helpdesk #7062]
>
> in the subject line of subsequent emails.
>
> Thank you,
> Linux Foundation Support Team
>
> -------------------------------------------------------------------------
> Hi Randy,
>
> On Fri, 12 Sep 2014 10:39:19 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> > On 09/12/14 00:38, Stephen Rothwell wrote:
> > >
> > > Changes since 20140911:
> > >
> > ---------------------------------------------------------------------
> > >
> > > I have created today's linux-next tree at
> > > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > > (patches at http://www.kernel.org/pub/linux/kernel/next/ ).
> >
> > No patch tarball?
>
> Hmm, sorry I didn't notice this:
>
> Pushing patch to kernel.org ...
> patch-v3.17-rc4-next-20140912 (1/1)
> 100 % 2,494.2 KiB / 15.7 MiB = 0.155 1.9 MiB/s 0:08
> 2554072 [==================================================] 100%
> Compressing: .gz: 100% .xz: 100%
> Calculating sha256 for /pub/linux/kernel/next/patch-v3.17-rc4-next-20140912.gz ... logged.
> Cannot open lock file
>
> Helpdesk folks: is this expected? This is a put of
> patch-v3.17-rc4-next-20140912.xz using kup.
>
> Randy: I will try to reupload the patch
The reupload worked.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #1.2: Type: application/x-rt-original-message, Size: 5019 bytes --]
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-09-13 2:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-7062@linuxfoundation.org>
2014-09-12 7:38 ` linux-next: Tree for Sep 12 Stephen Rothwell
2014-09-12 17:39 ` Randy Dunlap
2014-09-13 1:59 ` Stephen Rothwell
[not found] ` <rt-3.8.13-21049-1410573601-1407.7062-3-0@linuxfoundation.org>
[not found] ` <20140913120848.243db589@canb.auug.org.au>
2014-09-13 2:08 ` sfr@canb.auug.org.au via RT [this message]
2014-09-13 2:09 ` 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=rt-3.8.13-21021-1410574137-1910.7062-6-0@linuxfoundation.org \
--to=kernel-helpdesk@rt.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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).