From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Corey Minyard <minyard@acm•org>
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: Tue, 24 Feb 2015 09:54:49 +1100 [thread overview]
Message-ID: <20150224095449.243040b5@canb.auug.org.au> (raw)
In-Reply-To: <54EB9F33.6030702@acm.org>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
Hi Corey,
On Mon, 23 Feb 2015 15:44:19 -0600 Corey Minyard <minyard@acm•org> wrote:
>
> 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.
I see the problem. I expect for-next to be a branch, but it is a tag.
It is a real pain to pull a tag into a shared tree like mine (there
could be a for-next tag in every tree I fetch from ...).
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-23 22:54 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
2015-02-23 22:54 ` Stephen Rothwell [this message]
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=20150224095449.243040b5@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=cminyard@mvista$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=minyard@acm$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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