From: Dave Chinner <david@fromorbit.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [ANNOUNCE] xfstests: master branch updated to efef020df5b2
Date: Mon, 31 Oct 2016 23:00:54 +1100 [thread overview]
Message-ID: <20161031120054.GS14023@dastard> (raw)
In-Reply-To: <20161031073116.GO27776@eguan.usersys.redhat.com>
On Mon, Oct 31, 2016 at 03:31:16PM +0800, Eryu Guan wrote:
> Hi Dave,
>
> On Mon, Oct 31, 2016 at 04:19:19PM +1100, Dave Chinner wrote:
> > Hi folks,
> >
> > The master branch of the xfstests repository at:
> >
> > git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
> >
> > have just been updated. Thatnks to everyone who added tests, fixed
>
> Thanks for the update! But I don't see it in master branch, 'git pull'
> fetched nothing, and master HEAD still points to "16ef084 xfs/122:
> remove dead code".
>
> Is there any latency from kernel.org so that I only have to wait for
> more time? Or something went wrong with the push?
No idea what went wrong there. I pushed, logged in and then switched
windows to write the email. For the first time in an awful long
time, I didn't bother to check that the push finished and the branch
was updated on kernel.org. Turns out something went wrong mid push -
looking at the logs on various machines round here I think the net
connection on my end went down, and when it reconnected I got a
different IP address and so the push failed without me actually
noticing...
I just repushed, and it has completed from my end, and the web
interface on git.kernel.org now registers it.
Thanks for letting me know somehting went wrong!
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2016-10-31 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 5:19 [ANNOUNCE] xfstests: master branch updated to efef020df5b2 Dave Chinner
2016-10-31 7:31 ` Eryu Guan
2016-10-31 7:37 ` Darrick J. Wong
2016-10-31 12:00 ` Dave Chinner [this message]
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=20161031120054.GS14023@dastard \
--to=david@fromorbit.com \
--cc=eguan@redhat.com \
--cc=fstests@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