Andrew
at 23.06.2011 16:02, Andrew wrote:
> 23.06.2011 16:18, Erich Titl пишет:
>> Hi Andrew
>>
...
>>> On what branch you are now (do 'git branch')?
>> mega@luna:~/leaf/devel/leaf> git branch
>>experimental
>> * master
>> mega@luna:~/leaf/devel/leaf> ls
>> bering-uclibc4 buildlwp.sh
23.06.2011 16:18, Erich Titl пишет:
> Hi Andrew
>
> at 23.06.2011 13:30, Andrew wrote:
>> 23.06.2011 10:07, Erich Titl пишет:
>>> Hi Andrew
>>>
>>> at 23.06.2011 00:56, Andrew wrote:
23.06.2011 00:19, Erich Titl пишет:
>>>
>>>
It seems that you have at least one unpushed commit.
Hi Andrew
at 23.06.2011 13:30, Andrew wrote:
> 23.06.2011 10:07, Erich Titl пишет:
>> Hi Andrew
>>
>> at 23.06.2011 00:56, Andrew wrote:
>>> 23.06.2011 00:19, Erich Titl пишет:
>>
>>
>>> It seems that you have at least one unpushed commit.
>>> Easiest and most predictable way to resolve this
23.06.2011 10:07, Erich Titl пишет:
> Hi Andrew
>
> at 23.06.2011 00:56, Andrew wrote:
>> 23.06.2011 00:19, Erich Titl пишет:
>
>
>> It seems that you have at least one unpushed commit.
>> Easiest and most predictable way to resolve this IMHO todo next steps:
>> 1) Mark this commit as new bran
23.06.2011 09:33, Erich Titl пишет:
> Hi Andrew
>
> at 23.06.2011 00:56, Andrew wrote:
>> 23.06.2011 00:19, Erich Titl пишет:
>>> on 22.06.2011 22:03, Andrew wrote:
22.06.2011 22:15, Erich Titl пишет:
> HI Andrew
>
>>> ...
> git pull
> et...@leaf.git.sourceforge.net's password:
Hi Andrew
at 23.06.2011 00:56, Andrew wrote:
> 23.06.2011 00:19, Erich Titl пишет:
>>
> It seems that you have at least one unpushed commit.
> Easiest and most predictable way to resolve this IMHO todo next steps:
> 1) Mark this commit as new branch (git branch experimental)
> 2) Rollback to
