From: Christoph Hellwig <hch@lst.de>
To: xfs-masters@oss.sgi.com
Cc: git@vger.kernel.org
Subject: Re: [xfs-masters] git://oss.sgi.com broke
Date: Fri, 3 Oct 2008 21:27:40 +0200 [thread overview]
Message-ID: <20081003192740.GA16438@lst.de> (raw)
In-Reply-To: <20081003121903.6c9a7ebc.akpm@linux-foundation.org>
On Fri, Oct 03, 2008 at 12:19:03PM -0700, Andrew Morton wrote:
> It was OK yesterday.
>
> (cc'ing the git list in case this is an faq?)
>
> The last two error messages there look wrong/misleading?
Git pull still works fine for me..
next prev parent reply other threads:[~2008-10-03 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 19:19 git://oss.sgi.com broke Andrew Morton
2008-10-03 19:27 ` Christoph Hellwig [this message]
2008-10-06 16:31 ` [xfs-masters] " Russell Cattelan
2008-10-06 17:34 ` Samuel Tardieu
2008-10-06 17:37 ` Samuel Tardieu
2008-10-06 17:14 ` Linus Torvalds
2008-10-06 17:58 ` Daniel Barkalow
2008-10-07 17:32 ` Andrew Morton
2008-10-06 17:30 ` [xfs-masters] " Russell Cattelan
2008-10-07 17:39 ` Andrew Morton
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=20081003192740.GA16438@lst.de \
--to=hch@lst.de \
--cc=git@vger.kernel.org \
--cc=xfs-masters@oss.sgi.com \
/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).