On 08/05/2014 02:07 PM, Yves Blusseau wrote:
-snip-
> Humm it's seems there are new commits in the next branch, but i don't see
> where it came from.
> We must see only merges in next branch. And actually i only see master and
> kernel-3.14 that can be merge into next ?
-snip-
https://sourceforg
Le 5 août 2014 à 17:13, kp kirchdoerfer a écrit :
> Am Mittwoch, 30. Juli 2014, 23:47:16 schrieb Yves Blusseau:
>> Le 30 juil. 2014 à 17:48, kp kirchdoerfer a
> écrit :
>>> Am Dienstag, 29. Juli 2014, 18:17:56 schrieb Yves Blusseau:
Hi all,
i think you are misusing the next bra
Am Mittwoch, 30. Juli 2014, 23:47:16 schrieb Yves Blusseau:
> Le 30 juil. 2014 à 17:48, kp kirchdoerfer a
écrit :
> > Am Dienstag, 29. Juli 2014, 18:17:56 schrieb Yves Blusseau:
> >> Hi all,
> >>
> >> i think you are misusing the next branch.
> >> The next branch is not use to be the next branch
Le 30 juil. 2014 à 17:48, kp kirchdoerfer a
écrit :
> Am Dienstag, 29. Juli 2014, 18:17:56 schrieb Yves Blusseau:
>> Hi all,
>>
>> i think you are misusing the next branch.
>> The next branch is not use to be the next branch for the next release. As
>> the git workflow guide said (http://goo.g
Am Dienstag, 29. Juli 2014, 18:17:56 schrieb Yves Blusseau:
> Hi all,
>
> i think you are misusing the next branch.
> The next branch is not use to be the next branch for the next release. As
> the git workflow guide said (http://goo.gl/BOzkap) the next branch is
> intended as a testing branch for
29.07.2014 22:53, Yves Blusseau пишет:
> Le 29 juil. 2014 à 21:35, Andrew a écrit :
>
>> Fixed. I've cherry-picked significant commits into kernel-3.14, and
>> forced next branch to point at current master branch.
>>
>> For all, you need to do `git reset --hard origin/next` on next branch,
>> if i
Le 29 juil. 2014 à 21:35, Andrew a écrit :
> Fixed. I've cherry-picked significant commits into kernel-3.14, and
> forced next branch to point at current master branch.
>
> For all, you need to do `git reset --hard origin/next` on next branch,
> if it is in your local repo.
Thanks andrew.
Le 29 juil. 2014 à 20:21, Erich Titl a écrit :
> Hi Yves
>
> at 29.07.2014 18:17, Yves Blusseau wrote:
>> Hi all,
>>
>> i think you are misusing the next branch.
>> The next branch is not use to be the next branch for the next release. As
>> the git workflow guide said (http://goo.gl/BOzkap)
Fixed. I've cherry-picked significant commits into kernel-3.14, and
forced next branch to point at current master branch.
For all, you need to do `git reset --hard origin/next` on next branch,
if it is in your local repo.
29.07.2014 19:17, Yves Blusseau пишет:
> Hi all,
>
> i think you are misu
Hi Yves
at 29.07.2014 18:17, Yves Blusseau wrote:
> Hi all,
>
> i think you are misusing the next branch.
> The next branch is not use to be the next branch for the next release. As the
> git workflow guide said (http://goo.gl/BOzkap) the next branch is intended as
> a testing branch for topics
Hi all,
i think you are misusing the next branch.
The next branch is not use to be the next branch for the next release. As the
git workflow guide said (http://goo.gl/BOzkap) the next branch is intended as a
testing branch for topics being tested for stability for master.
So the next branch is u
11 matches
Mail list logo