On 8 July 2011 12:50, john stultz wrote:
> On Fri, 2011-07-08 at 12:35 -0700, Deepak Saxena wrote:
>> On 1 July 2011 12:14, Deepak Saxena wrote:
>> > Each of the trees have various tags and branches based on how each
>> > team and developer
>> > works and I don't want to ask folks to change what
On Fri, 2011-07-08 at 12:35 -0700, Deepak Saxena wrote:
> On 1 July 2011 12:14, Deepak Saxena wrote:
> > Each of the trees have various tags and branches based on how each
> > team and developer
> > works and I don't want to ask folks to change what they are doing for
> > their day to work.
> > Wh
On 1 July 2011 12:14, Deepak Saxena wrote:
> Each of the trees have various tags and branches based on how each
> team and developer
> works and I don't want to ask folks to change what they are doing for
> their day to work.
> What I'd like to see is a a separate set of official trees that only
>
On 1 July 2011 12:21, Andy Green wrote:
> On 07/01/2011 08:14 PM, Somebody in the thread at some point said:
>
>> What I'd like to see is a a separate set of official trees that only
>> get updated with bits that
>> we are ready for non-Linaro developers to use, do not get rebased, and
>> get tagg
On Mon, Jul 4, 2011 at 11:31 AM, Andy Green wrote:
> On 07/04/2011 10:25 AM, Somebody in the thread at some point said:
>>
>> On Fri, Jul 1, 2011 at 9:21 PM, Andy Green wrote:
>>>
>>> It would be less ridiculous than issuing monthly tarballs for the kernel
>>> case.
>>
>> why do you think that ta
On 07/04/2011 10:25 AM, Somebody in the thread at some point said:
On Fri, Jul 1, 2011 at 9:21 PM, Andy Green wrote:
It would be less ridiculous than issuing monthly tarballs for the kernel
case.
why do you think that tarballs are ridiculous? even kernel.org
releases tarballs last I looked.
On Fri, Jul 1, 2011 at 9:21 PM, Andy Green wrote:
>
> It would be less ridiculous than issuing monthly tarballs for the kernel
> case.
why do you think that tarballs are ridiculous? even kernel.org
releases tarballs last I looked. IMO you can prefectly have tags +
tarballs coexist and everbody wo
On 07/01/2011 08:14 PM, Somebody in the thread at some point said:
What I'd like to see is a a separate set of official trees that only
get updated with bits that
we are ready for non-Linaro developers to use, do not get rebased, and
get tagged at the
end of each monthly cycle. My proposal:
ker
Hi all,
I was looking at git.linaro.org and I'd like to propose some consistency
in naming our git trees and in how we branch them. The main reason
for this from my perspective is to make it easy to point someone
from a partner team or from a partner''s customer to the git server and
have them qui