linux-kernel - Re: linux-next: error fetching the ipmi tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Feb 2015 18:06:54 -0600
From:	Corey Minyard <minyard@....org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Corey Minyard <cminyard@...sta.com>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: linux-next: error fetching the ipmi tree

On 02/23/2015 04:54 PM, Stephen Rothwell wrote:
> Hi Corey,
>
> On Mon, 23 Feb 2015 15:44:19 -0600 Corey Minyard <minyard@....org> wrote:
>> Sourcefoge is definitely having issues:
>>
>>     [cminyard@...0 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 ...).
Oops, I messed that up, I mixing up procedures.  It's fixed.

-corey
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/