From: Corey Minyard <minyard@acm.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Corey Minyard <cminyard@mvista.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: error fetching the ipmi tree
Date: Mon, 23 Feb 2015 15:44:19 -0600 [thread overview]
Message-ID: <54EB9F33.6030702@acm.org> (raw)
In-Reply-To: <20150224072004.534ccb5a@canb.auug.org.au>
Sourcefoge is definitely having issues:
[cminyard@t430 linux-ipmi]$ git push origin for-next
fatal: '/git/p/openipmi/linux-ipmi' does not appear to be a git
repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
After a while it started working, and the tag was there. I've verified
that everything is ok from a different machine.
-corey
On 02/23/2015 02:20 PM, Stephen Rothwell wrote:
> Hi Corey,
>
> On Sun, 22 Feb 2015 20:12:41 -0600 Corey Minyard <minyard@acm.org> wrote:
>> On 02/22/2015 05:23 PM, Stephen Rothwell wrote:
>>> While fetching the ipmi tree
>>> (git://git.code.sf.net/p/openipmi/linux-ipmi#for-next), I get this
>>> error:
>>>
>>> fatal: Couldn't find remote ref refs/heads/for-next
>>>
>> Hmm, I haven't touched that tag. Sourceforge has been doing some
>> strange things lately, I'm wondering if I should switch to something
>> else. I guess I could have accidentally deleted it, too.
>>
>> Anyway, those changes are all in Linus' tree, so I just moved for-next
>> to master.
> Its gone again :-(
>
next prev parent reply other threads:[~2015-02-23 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 23:23 linux-next: error fetching the ipmi tree Stephen Rothwell
2015-02-23 2:12 ` Corey Minyard
2015-02-23 20:20 ` Stephen Rothwell
2015-02-23 21:44 ` Corey Minyard [this message]
2015-02-23 22:54 ` Stephen Rothwell
2015-02-24 0:06 ` Corey Minyard
2015-02-24 0:27 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2015-07-21 22:29 Stephen Rothwell
2015-07-21 23:45 ` Corey Minyard
2015-07-22 1:03 ` Stephen Rothwell
2017-02-19 21:00 ` Stephen Rothwell
2017-02-19 22:26 ` Corey Minyard
2017-02-19 23:33 ` Stephen Rothwell
2017-03-09 21:41 ` Corey Minyard
2017-03-09 23:48 ` 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=54EB9F33.6030702@acm.org \
--to=minyard@acm.org \
--cc=cminyard@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.