Am 19.12.2012 15:27, schrieb KP Kirchdoerfer:
> Am 19.12.2012 14:47, schrieb Mike Noyes:
>> On 12/19/2012 01:36 AM, KP Kirchdoerfer wrote:
>>> Am 17.12.2012 14:58, schrieb Mike Noyes:
>>>> On 12/17/2012 03:17 AM, Yves Blusseau wrote:
>>>>> Hi all,
>>>>>
>>>>> i see some commits that has been done in the old git repository:
>>>>>
>>>>> $ git cherry -v origin/master old/master
>>>>> + 7127babead986725fc128e9acc7b1c5a08fa44d8 kernel update to 3.2.35
>>>>> + b3b98c475e6392a92951c3b29445d3db86c9a7f6 add verification with gpgv
>>>>>
>>>>> I have merge the changes in the new git repository but don't forget to 
>>>>> change the URL of the new git repository with a command like this:
>>>>>
>>>>> git remote set-url origin 
>>>>> ssh://yourn...@git.code.sf.net/p/leaf/bering-uclibc
>>>>
>>>> Yves,
>>>> Thanks for catching this issue.
>>>>
>>>
>>> Hi;
>>>
>>> does this mean
>>>
>>> http://leaf.git.sourceforge.net/git/gitweb.cgi?p=leaf/bering-uclibc;a=summary
>>>
>>> is outdated?
>> 
>> KP,
>> Yes.
>> 
>>> And the new URL to browse the git repository is this one?
>>> http://sourceforge.net/p/leaf/bering-uclibc/commit_browser
>> 
>> Correct.
>> 
>>> In that case it seems not to be updated, the latest commits by Yves are
>>> not shown.
>> 
>> I see three commits [ce11cc], [18e8f8] and, [17fa94]) from Yves two days 
>> ago.
> 
> My fault.
> 
>> I also see the two [5edf97], and [25b53c] from you today.
> 
> When logged in and trying to follow the links I get an error message
> from SF ("Oops, looks like something went wrong"). It works if I'm not
> logged in.

Hi Mike;

the allura git browser is a pain.

I've checked again, and now, regardless if logged in or out, I do have
the same issues as above when I click "History".

Another flaw is that I sometimes get the option to "Log In" but none to
"Log out". If I get the option to logout via menu I'll end up in
"sourceforge.net" but not in the same space I logged out.

And even more worse, I've seen today it almostly worked, but either it's
a UI issue and I can't find it, or it fails too often.
Either way it really needs some hands on to be on par with the old cgi
page.

With the working commit-mailinglist and a local git browser it should be
possible to work around the issues. Shurely not your fault, but
hopefully your contacts to SF team will help to solve the remaining issues.

kp

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to