Nexus S went on sale yesterday morning in the US, running Gingerbread. Just like I did for Froyo, I'm open-sourcing the matching Android platform source code, right after the first consumers get their hands on it. I'm going to start literally right now, and the process will take a few hours.
I'll give more details once the source code is available. However, there are three aspects that you need to know ahead of time:
-As part of the process to push the source code, there will be some points in time when the master branch doesn't build. Sorry about that. If you're working on the master branch, I recommend that you don't sync until I send an "all clear" when I'm done and things look good. Other branches are expected to work fine as soon as their manifests are created.
-Even though Nexus S is designed to be suitable for AOSP work, there are some caveats. I very strongly recommend against trying to use Nexus S for anything related to AOSP at the moment. Trying to unlock or use your Nexus S for AOSP work could easily turn it into a Nexus B (where B means "brick"); I have two of those, they're not very useful. I'll send some guidelines about what is currently possible once I've finished pushing the source code.
-Please take it easy on the kernel.org servers. They are very helpful in hosting the AOSP source code, and I don't want to hurt the high quality of their service with an onslaught of full Android downloads. If you're not going to immediately work on porting Gingerbread to devices with the intent of distributing the result to end-users, I'm kindly asking that you wait a few hours or a few days before you download it (just roll a 6-sided die and wait that long). In addition, the slower the servers are, the harder it is for me to do the push.
> Nexus S went on sale yesterday morning in the US, running Gingerbread.
> Just like I did for Froyo, I'm open-sourcing the matching Android
> platform source code, right after the first consumers get their hands
> on it. I'm going to start literally right now, and the process will
> take a few hours.
> I'll give more details once the source code is available. However,
> there are three aspects that you need to know ahead of time:
> -As part of the process to push the source code, there will be some
> points in time when the master branch doesn't build. Sorry about that.
> If you're working on the master branch, I recommend that you don't
> sync until I send an "all clear" when I'm done and things look good.
> Other branches are expected to work fine as soon as their manifests
> are created.
> -Even though Nexus S is designed to be suitable for AOSP work, there
> are some caveats. I very strongly recommend against trying to use
> Nexus S for anything related to AOSP at the moment. Trying to unlock
> or use your Nexus S for AOSP work could easily turn it into a Nexus B
> (where B means "brick"); I have two of those, they're not very useful.
> I'll send some guidelines about what is currently possible once I've
> finished pushing the source code.
> -Please take it easy on the kernel.org servers. They are very helpful
> in hosting the AOSP source code, and I don't want to hurt the high
> quality of their service with an onslaught of full Android downloads.
> If you're not going to immediately work on porting Gingerbread to
> devices with the intent of distributing the result to end-users, I'm
> kindly asking that you wait a few hours or a few days before you
> download it (just roll a 6-sided die and wait that long). In addition,
> the slower the servers are, the harder it is for me to do the push.
> Questions sent directly to me that have no reason for being private
> will likely get ignored or forwarded to a public forum with no further
> warning.
> Nexus S went on sale yesterday morning in the US, running Gingerbread.
> Just like I did for Froyo, I'm open-sourcing the matching Android
> platform source code, right after the first consumers get their hands
> on it. I'm going to start literally right now, and the process will
> take a few hours.
> I'll give more details once the source code is available. However,
> there are three aspects that you need to know ahead of time:
> -As part of the process to push the source code, there will be some
> points in time when the master branch doesn't build. Sorry about that.
> If you're working on the master branch, I recommend that you don't
> sync until I send an "all clear" when I'm done and things look good.
> Other branches are expected to work fine as soon as their manifests
> are created.
> -Even though Nexus S is designed to be suitable for AOSP work, there
> are some caveats. I very strongly recommend against trying to use
> Nexus S for anything related to AOSP at the moment. Trying to unlock
> or use your Nexus S for AOSP work could easily turn it into a Nexus B
> (where B means "brick"); I have two of those, they're not very useful.
> I'll send some guidelines about what is currently possible once I've
> finished pushing the source code.
> -Please take it easy on the kernel.org servers. They are very helpful
> in hosting the AOSP source code, and I don't want to hurt the high
> quality of their service with an onslaught of full Android downloads.
> If you're not going to immediately work on porting Gingerbread to
> devices with the intent of distributing the result to end-users, I'm
> kindly asking that you wait a few hours or a few days before you
> download it (just roll a 6-sided die and wait that long). In addition,
> the slower the servers are, the harder it is for me to do the push.
> Questions sent directly to me that have no reason for being private
> will likely get ignored or forwarded to a public forum with no further
> warning.
> Nexus S went on sale yesterday morning in the US, running Gingerbread. > Just like I did for Froyo, I'm open-sourcing the matching Android > platform source code, right after the first consumers get their hands > on it. I'm going to start literally right now, and the process will > take a few hours.
> I'll give more details once the source code is available. However, > there are three aspects that you need to know ahead of time:
> -As part of the process to push the source code, there will be some > points in time when the master branch doesn't build. Sorry about that. > If you're working on the master branch, I recommend that you don't > sync until I send an "all clear" when I'm done and things look good. > Other branches are expected to work fine as soon as their manifests > are created.
> -Even though Nexus S is designed to be suitable for AOSP work, there > are some caveats. I very strongly recommend against trying to use > Nexus S for anything related to AOSP at the moment. Trying to unlock > or use your Nexus S for AOSP work could easily turn it into a Nexus B > (where B means "brick"); I have two of those, they're not very useful. > I'll send some guidelines about what is currently possible once I've > finished pushing the source code.
> -Please take it easy on the kernel.org servers. They are very helpful > in hosting the AOSP source code, and I don't want to hurt the high > quality of their service with an onslaught of full Android downloads. > If you're not going to immediately work on porting Gingerbread to > devices with the intent of distributing the result to end-users, I'm > kindly asking that you wait a few hours or a few days before you > download it (just roll a 6-sided die and wait that long). In addition, > the slower the servers are, the harder it is for me to do the push.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
> -- > You received this message because you are subscribed to the "Android Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
Wow, youre hard working! So its not the best time to start a master? As i just installed 64environment... Am 17.12.2010 18:44 schrieb "Jean-Baptiste Queru" <j...@android.com>:
> Nexus S went on sale yesterday morning in the US, running Gingerbread. > Just like I did for Froyo, I'm open-sourcing the matching Android > platform source code, right after the first consumers get their hands > on it. I'm going to start literally right now, and the process will > take a few hours.
> I'll give more details once the source code is available. However, > there are three aspects that you need to know ahead of time:
> -As part of the process to push the source code, there will be some > points in time when the master branch doesn't build. Sorry about that. > If you're working on the master branch, I recommend that you don't > sync until I send an "all clear" when I'm done and things look good. > Other branches are expected to work fine as soon as their manifests > are created.
> -Even though Nexus S is designed to be suitable for AOSP work, there > are some caveats. I very strongly recommend against trying to use > Nexus S for anything related to AOSP at the moment. Trying to unlock > or use your Nexus S for AOSP work could easily turn it into a Nexus B > (where B means "brick"); I have two of those, they're not very useful. > I'll send some guidelines about what is currently possible once I've > finished pushing the source code.
> -Please take it easy on the kernel.org servers. They are very helpful > in hosting the AOSP source code, and I don't want to hurt the high > quality of their service with an onslaught of full Android downloads. > If you're not going to immediately work on porting Gingerbread to > devices with the intent of distributing the result to end-users, I'm > kindly asking that you wait a few hours or a few days before you > download it (just roll a 6-sided die and wait that long). In addition, > the slower the servers are, the harder it is for me to do the push.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
> -- > You received this message because you are subscribed to the "Android
> To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
> Nexus S went on sale yesterday morning in the US, running Gingerbread.
> Just like I did for Froyo, I'm open-sourcing the matching Android
> platform source code, right after the first consumers get their hands
> on it. I'm going to start literally right now, and the process will
> take a few hours.
> I'll give more details once the source code is available. However,
> there are three aspects that you need to know ahead of time:
> -As part of the process to push the source code, there will be some
> points in time when the master branch doesn't build. Sorry about that.
> If you're working on the master branch, I recommend that you don't
> sync until I send an "all clear" when I'm done and things look good.
> Other branches are expected to work fine as soon as their manifests
> are created.
> -Even though Nexus S is designed to be suitable for AOSP work, there
> are some caveats. I very strongly recommend against trying to use
> Nexus S for anything related to AOSP at the moment. Trying to unlock
> or use your Nexus S for AOSP work could easily turn it into a Nexus B
> (where B means "brick"); I have two of those, they're not very useful.
> I'll send some guidelines about what is currently possible once I've
> finished pushing the source code.
> -Please take it easy on the kernel.org servers. They are very helpful
> in hosting the AOSP source code, and I don't want to hurt the high
> quality of their service with an onslaught of full Android downloads.
> If you're not going to immediately work on porting Gingerbread to
> devices with the intent of distributing the result to end-users, I'm
> kindly asking that you wait a few hours or a few days before you
> download it (just roll a 6-sided die and wait that long). In addition,
> the slower the servers are, the harder it is for me to do the push.
> Questions sent directly to me that have no reason for being private
> will likely get ignored or forwarded to a public forum with no further
> warning.
On Fri, Dec 17, 2010 at 10:39 AM, A.C. <cenicero...@gmail.com> wrote: > So this is merging straight into Master and not to a separate branch?
> On Dec 17, 12:44 pm, Jean-Baptiste Queru <j...@android.com> wrote: >> Nexus S went on sale yesterday morning in the US, running Gingerbread. >> Just like I did for Froyo, I'm open-sourcing the matching Android >> platform source code, right after the first consumers get their hands >> on it. I'm going to start literally right now, and the process will >> take a few hours.
>> I'll give more details once the source code is available. However, >> there are three aspects that you need to know ahead of time:
>> -As part of the process to push the source code, there will be some >> points in time when the master branch doesn't build. Sorry about that. >> If you're working on the master branch, I recommend that you don't >> sync until I send an "all clear" when I'm done and things look good. >> Other branches are expected to work fine as soon as their manifests >> are created.
>> -Even though Nexus S is designed to be suitable for AOSP work, there >> are some caveats. I very strongly recommend against trying to use >> Nexus S for anything related to AOSP at the moment. Trying to unlock >> or use your Nexus S for AOSP work could easily turn it into a Nexus B >> (where B means "brick"); I have two of those, they're not very useful. >> I'll send some guidelines about what is currently possible once I've >> finished pushing the source code.
>> -Please take it easy on the kernel.org servers. They are very helpful >> in hosting the AOSP source code, and I don't want to hurt the high >> quality of their service with an onslaught of full Android downloads. >> If you're not going to immediately work on porting Gingerbread to >> devices with the intent of distributing the result to end-users, I'm >> kindly asking that you wait a few hours or a few days before you >> download it (just roll a 6-sided die and wait that long). In addition, >> the slower the servers are, the harder it is for me to do the push.
>> Questions sent directly to me that have no reason for being private >> will likely get ignored or forwarded to a public forum with no further >> warning.
> -- > You received this message because you are subscribed to the "Android Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
> I'll be creating a tagged version of 2.3 which will match the exact > code that is used on Nexus S.
> I'll also be creating a new branch for gingerbread, which will mirror > the development branch that's been used by Google engineers.
> Finally, that gingerbread branch will be merged with the master > branch, which is essentially a very large contribution to AOSP.
> JBQ
> On Fri, Dec 17, 2010 at 10:39 AM, A.C. <cenicero...@gmail.com> wrote: > > So this is merging straight into Master and not to a separate branch?
> > On Dec 17, 12:44 pm, Jean-Baptiste Queru <j...@android.com> wrote: > >> Nexus S went on sale yesterday morning in the US, running Gingerbread. > >> Just like I did for Froyo, I'm open-sourcing the matching Android > >> platform source code, right after the first consumers get their hands > >> on it. I'm going to start literally right now, and the process will > >> take a few hours.
> >> I'll give more details once the source code is available. However, > >> there are three aspects that you need to know ahead of time:
> >> -As part of the process to push the source code, there will be some > >> points in time when the master branch doesn't build. Sorry about that. > >> If you're working on the master branch, I recommend that you don't > >> sync until I send an "all clear" when I'm done and things look good. > >> Other branches are expected to work fine as soon as their manifests > >> are created.
> >> -Even though Nexus S is designed to be suitable for AOSP work, there > >> are some caveats. I very strongly recommend against trying to use > >> Nexus S for anything related to AOSP at the moment. Trying to unlock > >> or use your Nexus S for AOSP work could easily turn it into a Nexus B > >> (where B means "brick"); I have two of those, they're not very useful. > >> I'll send some guidelines about what is currently possible once I've > >> finished pushing the source code.
> >> -Please take it easy on the kernel.org servers. They are very helpful > >> in hosting the AOSP source code, and I don't want to hurt the high > >> quality of their service with an onslaught of full Android downloads. > >> If you're not going to immediately work on porting Gingerbread to > >> devices with the intent of distributing the result to end-users, I'm > >> kindly asking that you wait a few hours or a few days before you > >> download it (just roll a 6-sided die and wait that long). In addition, > >> the slower the servers are, the harder it is for me to do the push.
> >> Questions sent directly to me that have no reason for being private > >> will likely get ignored or forwarded to a public forum with no further > >> warning.
> > -- > > You received this message because you are subscribed to the "Android > Building" mailing list. > > To post to this group, send email to android-building@googlegroups.com > > To unsubscribe from this group, send email to > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@googlegroups.com> > > For more options, visit this group at > > http://groups.google.com/group/android-building?hl=en
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
> -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
Are there any caveats to making a build for an ADP device that aren't
addressed in the current directions on source.android.com, including
the Nexus One?
On Dec 17, 1:47 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> I'll be creating a tagged version of 2.3 which will match the exact
> code that is used on Nexus S.
> I'll also be creating a new branch for gingerbread, which will mirror
> the development branch that's been used by Google engineers.
> Finally, that gingerbread branch will be merged with the master
> branch, which is essentially a very large contribution to AOSP.
> JBQ
> On Fri, Dec 17, 2010 at 10:39 AM, A.C. <cenicero...@gmail.com> wrote:
> > So this is merging straight into Master and not to a separate branch?
> > On Dec 17, 12:44 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> >> Nexus S went on sale yesterday morning in the US, running Gingerbread.
> >> Just like I did for Froyo, I'm open-sourcing the matching Android
> >> platform source code, right after the first consumers get their hands
> >> on it. I'm going to start literally right now, and the process will
> >> take a few hours.
> >> I'll give more details once the source code is available. However,
> >> there are three aspects that you need to know ahead of time:
> >> -As part of the process to push the source code, there will be some
> >> points in time when the master branch doesn't build. Sorry about that.
> >> If you're working on the master branch, I recommend that you don't
> >> sync until I send an "all clear" when I'm done and things look good.
> >> Other branches are expected to work fine as soon as their manifests
> >> are created.
> >> -Even though Nexus S is designed to be suitable for AOSP work, there
> >> are some caveats. I very strongly recommend against trying to use
> >> Nexus S for anything related to AOSP at the moment. Trying to unlock
> >> or use your Nexus S for AOSP work could easily turn it into a Nexus B
> >> (where B means "brick"); I have two of those, they're not very useful.
> >> I'll send some guidelines about what is currently possible once I've
> >> finished pushing the source code.
> >> -Please take it easy on the kernel.org servers. They are very helpful
> >> in hosting the AOSP source code, and I don't want to hurt the high
> >> quality of their service with an onslaught of full Android downloads.
> >> If you're not going to immediately work on porting Gingerbread to
> >> devices with the intent of distributing the result to end-users, I'm
> >> kindly asking that you wait a few hours or a few days before you
> >> download it (just roll a 6-sided die and wait that long). In addition,
> >> the slower the servers are, the harder it is for me to do the push.
> >> Questions sent directly to me that have no reason for being private
> >> will likely get ignored or forwarded to a public forum with no further
> >> warning.
> > --
> > You received this message because you are subscribed to the "Android Building" mailing list.
> > To post to this group, send email to android-building@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/android-building?hl=en
> Questions sent directly to me that have no reason for being private
> will likely get ignored or forwarded to a public forum with no further
> warning.
Thank you for your hard working. I learned Android from here
everytime.
After finish pushing Gingerbread to AOSP,
I wish AOSP renew 'setting up your machine' at 'Get android source
code' : http://goo.gl/iWky I am little bit ambiguous about building android with 64bit recent
version of Ubuntu.
Anyhow, I wish gingerbread will be merged to AOSP perfectly then I
want to see you at andorid blog!
On 12월18일, 오전3시47분, Jean-Baptiste Queru <j...@android.com> wrote:
> I'll be creating a tagged version of 2.3 which will match the exact
> code that is used on Nexus S.
> I'll also be creating a new branch for gingerbread, which will mirror
> the development branch that's been used by Google engineers.
> Finally, that gingerbread branch will be merged with the master
> branch, which is essentially a very large contribution to AOSP.
> JBQ
> On Fri, Dec 17, 2010 at 10:39 AM, A.C. <cenicero...@gmail.com> wrote:
> > So this is merging straight into Master and not to a separate branch?
> > On Dec 17, 12:44 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> >> Nexus S went on sale yesterday morning in the US, running Gingerbread.
> >> Just like I did for Froyo, I'm open-sourcing the matching Android
> >> platform source code, right after the first consumers get their hands
> >> on it. I'm going to start literally right now, and the process will
> >> take a few hours.
> >> I'll give more details once the source code is available. However,
> >> there are three aspects that you need to know ahead of time:
> >> -As part of the process to push the source code, there will be some
> >> points in time when the master branch doesn't build. Sorry about that.
> >> If you're working on the master branch, I recommend that you don't
> >> sync until I send an "all clear" when I'm done and things look good.
> >> Other branches are expected to work fine as soon as their manifests
> >> are created.
> >> -Even though Nexus S is designed to be suitable for AOSP work, there
> >> are some caveats. I very strongly recommend against trying to use
> >> Nexus S for anything related to AOSP at the moment. Trying to unlock
> >> or use your Nexus S for AOSP work could easily turn it into a Nexus B
> >> (where B means "brick"); I have two of those, they're not very useful.
> >> I'll send some guidelines about what is currently possible once I've
> >> finished pushing the source code.
> >> -Please take it easy on the kernel.org servers. They are very helpful
> >> in hosting the AOSP source code, and I don't want to hurt the high
> >> quality of their service with an onslaught of full Android downloads.
> >> If you're not going to immediately work on porting Gingerbread to
> >> devices with the intent of distributing the result to end-users, I'm
> >> kindly asking that you wait a few hours or a few days before you
> >> download it (just roll a 6-sided die and wait that long). In addition,
> >> the slower the servers are, the harder it is for me to do the push.
> >> Questions sent directly to me that have no reason for being private
> >> will likely get ignored or forwarded to a public forum with no further
> >> warning.
> > --
> > You received this message because you are subscribed to the "Android Building" mailing list.
> > To post to this group, send email to android-building@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/android-building?hl=en
> Questions sent directly to me that have no reason for being private
> will likely get ignored or forwarded to a public forum with no further
> warning.
> Thank you for your hard working. I learned Android from here > everytime.
> After finish pushing Gingerbread to AOSP, > I wish AOSP renew 'setting up your machine' at 'Get android source > code' : http://goo.gl/iWky > I am little bit ambiguous about building android with 64bit recent > version of Ubuntu.
> Anyhow, I wish gingerbread will be merged to AOSP perfectly then I > want to see you at andorid blog!
> On 12월18일, 오전3시47분, Jean-Baptiste Queru <j...@android.com> wrote: > > All of the above :)
> > I'll be creating a tagged version of 2.3 which will match the exact > > code that is used on Nexus S.
> > I'll also be creating a new branch for gingerbread, which will mirror > > the development branch that's been used by Google engineers.
> > Finally, that gingerbread branch will be merged with the master > > branch, which is essentially a very large contribution to AOSP.
> > JBQ
> > On Fri, Dec 17, 2010 at 10:39 AM, A.C. <cenicero...@gmail.com> wrote: > > > So this is merging straight into Master and not to a separate branch?
> > > On Dec 17, 12:44 pm, Jean-Baptiste Queru <j...@android.com> wrote: > > >> Nexus S went on sale yesterday morning in the US, running Gingerbread. > > >> Just like I did for Froyo, I'm open-sourcing the matching Android > > >> platform source code, right after the first consumers get their hands > > >> on it. I'm going to start literally right now, and the process will > > >> take a few hours.
> > >> I'll give more details once the source code is available. However, > > >> there are three aspects that you need to know ahead of time:
> > >> -As part of the process to push the source code, there will be some > > >> points in time when the master branch doesn't build. Sorry about that. > > >> If you're working on the master branch, I recommend that you don't > > >> sync until I send an "all clear" when I'm done and things look good. > > >> Other branches are expected to work fine as soon as their manifests > > >> are created.
> > >> -Even though Nexus S is designed to be suitable for AOSP work, there > > >> are some caveats. I very strongly recommend against trying to use > > >> Nexus S for anything related to AOSP at the moment. Trying to unlock > > >> or use your Nexus S for AOSP work could easily turn it into a Nexus B > > >> (where B means "brick"); I have two of those, they're not very useful. > > >> I'll send some guidelines about what is currently possible once I've > > >> finished pushing the source code.
> > >> -Please take it easy on the kernel.org servers. They are very helpful > > >> in hosting the AOSP source code, and I don't want to hurt the high > > >> quality of their service with an onslaught of full Android downloads. > > >> If you're not going to immediately work on porting Gingerbread to > > >> devices with the intent of distributing the result to end-users, I'm > > >> kindly asking that you wait a few hours or a few days before you > > >> download it (just roll a 6-sided die and wait that long). In addition, > > >> the slower the servers are, the harder it is for me to do the push.
> > >> Questions sent directly to me that have no reason for being private > > >> will likely get ignored or forwarded to a public forum with no further > > >> warning.
> > > -- > > > You received this message because you are subscribed to the "Android > Building" mailing list. > > > To post to this group, send email to android-building@googlegroups.com > > > To unsubscribe from this group, send email to > > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@googlegroups.com> > > > For more options, visit this group at > > >http://groups.google.com/group/android-building?hl=en
> > Questions sent directly to me that have no reason for being private > > will likely get ignored or forwarded to a public forum with no further > > warning.
> -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
> > Thank you for your hard working. I learned Android from here
> > everytime.
> > After finish pushing Gingerbread to AOSP,
> > I wish AOSP renew 'setting up your machine' at 'Get android source
> > code' :http://goo.gl/iWky > > I am little bit ambiguous about building android with 64bit recent
> > version of Ubuntu.
> > Anyhow, I wish gingerbread will be merged to AOSP perfectly then I
> > want to see you at andorid blog!
> > On 12월18일, 오전3시47분, Jean-Baptiste Queru <j...@android.com> wrote:
> > > All of the above :)
> > > I'll be creating a tagged version of 2.3 which will match the exact
> > > code that is used on Nexus S.
> > > I'll also be creating a new branch for gingerbread, which will mirror
> > > the development branch that's been used by Google engineers.
> > > Finally, that gingerbread branch will be merged with the master
> > > branch, which is essentially a very large contribution to AOSP.
> > > JBQ
> > > On Fri, Dec 17, 2010 at 10:39 AM, A.C. <cenicero...@gmail.com> wrote:
> > > > So this is merging straight into Master and not to a separate branch?
> > > > On Dec 17, 12:44 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> > > >> Nexus S went on sale yesterday morning in the US, running Gingerbread.
> > > >> Just like I did for Froyo, I'm open-sourcing the matching Android
> > > >> platform source code, right after the first consumers get their hands
> > > >> on it. I'm going to start literally right now, and the process will
> > > >> take a few hours.
> > > >> I'll give more details once the source code is available. However,
> > > >> there are three aspects that you need to know ahead of time:
> > > >> -As part of the process to push the source code, there will be some
> > > >> points in time when the master branch doesn't build. Sorry about that.
> > > >> If you're working on the master branch, I recommend that you don't
> > > >> sync until I send an "all clear" when I'm done and things look good.
> > > >> Other branches are expected to work fine as soon as their manifests
> > > >> are created.
> > > >> -Even though Nexus S is designed to be suitable for AOSP work, there
> > > >> are some caveats. I very strongly recommend against trying to use
> > > >> Nexus S for anything related to AOSP at the moment. Trying to unlock
> > > >> or use your Nexus S for AOSP work could easily turn it into a Nexus B
> > > >> (where B means "brick"); I have two of those, they're not very useful.
> > > >> I'll send some guidelines about what is currently possible once I've
> > > >> finished pushing the source code.
> > > >> -Please take it easy on the kernel.org servers. They are very helpful
> > > >> in hosting the AOSP source code, and I don't want to hurt the high
> > > >> quality of their service with an onslaught of full Android downloads.
> > > >> If you're not going to immediately work on porting Gingerbread to
> > > >> devices with the intent of distributing the result to end-users, I'm
> > > >> kindly asking that you wait a few hours or a few days before you
> > > >> download it (just roll a 6-sided die and wait that long). In addition,
> > > >> the slower the servers are, the harder it is for me to do the push.
> > > >> Questions sent directly to me that have no reason for being private
> > > >> will likely get ignored or forwarded to a public forum with no further
> > > >> warning.
> > > > --
> > > > You received this message because you are subscribed to the "Android
> > Building" mailing list.
> > > > To post to this group, send email to android-building@googlegroups.com
> > > > To unsubscribe from this group, send email to
> > > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@googlegroups.com>
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/android-building?hl=en
> > > Questions sent directly to me that have no reason for being private
> > > will likely get ignored or forwarded to a public forum with no further
> > > warning.
> > --
> > You received this message because you are subscribed to the "Android
> > Building" mailing list.
> > To post to this group, send email to android-building@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@googlegroups.com>
> > For more options, visit this group at
> >http://groups.google.com/group/android-building?hl=en
> > > Thank you for your hard working. I learned Android from here
> > > everytime.
> > > After finish pushing Gingerbread to AOSP,
> > > I wish AOSP renew 'setting up your machine' at 'Get android source
> > > code' :http://goo.gl/iWky > > > I am little bit ambiguous about building android with 64bit recent
> > > version of Ubuntu.
> > > Anyhow, I wish gingerbread will be merged to AOSP perfectly then I
> > > want to see you at andorid blog!
> > > On 12월18일, 오전3시47분, Jean-Baptiste Queru <j...@android.com> wrote:
> > > > All of the above :)
> > > > I'll be creating a tagged version of 2.3 which will match the exact
> > > > code that is used on Nexus S.
> > > > I'll also be creating a new branch for gingerbread, which will mirror
> > > > the development branch that's been used by Google engineers.
> > > > Finally, that gingerbread branch will be merged with the master
> > > > branch, which is essentially a very large contribution to AOSP.
> > > > JBQ
> > > > On Fri, Dec 17, 2010 at 10:39 AM, A.C. <cenicero...@gmail.com> wrote:
> > > > > So this is merging straight into Master and not to a separate branch?
> > > > > On Dec 17, 12:44 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> > > > >> Nexus S went on sale yesterday morning in the US, running Gingerbread.
> > > > >> Just like I did for Froyo, I'm open-sourcing the matching Android
> > > > >> platform source code, right after the first consumers get their hands
> > > > >> on it. I'm going to start literally right now, and the process will
> > > > >> take a few hours.
> > > > >> I'll give more details once the source code is available. However,
> > > > >> there are three aspects that you need to know ahead of time:
> > > > >> -As part of the process to push the source code, there will be some
> > > > >> points in time when the master branch doesn't build. Sorry about that.
> > > > >> If you're working on the master branch, I recommend that you don't
> > > > >> sync until I send an "all clear" when I'm done and things look good.
> > > > >> Other branches are expected to work fine as soon as their manifests
> > > > >> are created.
> > > > >> -Even though Nexus S is designed to be suitable for AOSP work, there
> > > > >> are some caveats. I very strongly recommend against trying to use
> > > > >> Nexus S for anything related to AOSP at the moment. Trying to unlock
> > > > >> or use your Nexus S for AOSP work could easily turn it into a Nexus B
> > > > >> (where B means "brick"); I have two of those, they're not very useful.
> > > > >> I'll send some guidelines about what is currently possible once I've
> > > > >> finished pushing the source code.
> > > > >> -Please take it easy on the kernel.org servers. They are very helpful
> > > > >> in hosting the AOSP source code, and I don't want to hurt the high
> > > > >> quality of their service with an onslaught of full Android downloads.
> > > > >> If you're not going to immediately work on porting Gingerbread to
> > > > >> devices with the intent of distributing the result to end-users, I'm
> > > > >> kindly asking that you wait a few hours or a few days before you
> > > > >> download it (just roll a 6-sided die and wait that long). In addition,
> > > > >> the slower the servers are, the harder it is for me to do the push.
> > > > >> Thanks for being patient.
> > > > >> JBQ
> > > > >> Questions sent directly to me that have no reason for being private
> > > > >> will likely get ignored or forwarded to a public forum with no further
> > > > >> warning.
> > > > > --
> > > > > You received this message because you are subscribed to the "Android
> > > Building" mailing list.
> > > > > To post to this group, send email to android-building@googlegroups.com
> > > > > To unsubscribe from this group, send email to
> > > > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@googlegroups.com>
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/android-building?hl=en
> > > > Questions sent directly to me that have no reason for being private
> > > > will likely get ignored or forwarded to a public forum with no further
> > > > warning.
> > > --
> > > You received this message because you are subscribed to the "Android
> > > Building" mailing list.
> > > To post to this group, send email to android-building@googlegroups.com
> > > To unsubscribe from this group, send email to
> > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@googlegroups.com>
> > > For more options, visit this group at
> > >http://groups.google.com/group/android-building?hl=en
