FYI: Contributing to dalvik/libcore: small changes

37 views
Skip to first unread message

Jim Huang

unread,
Jun 23, 2012, 10:32:10 AM6/23/12
to 0xlab-devel
FYI.

In fact, it is as following:

dalvik$ git config -l | grep projectname
remote.aosp.projectname=platform/dalvik2

libcore$ git config -l | grep projectname
remote.aosp.projectname=platform/libcore2

---------- Forwarded message ----------
From: Jean-Baptiste Queru <j...@android.com>
Date: 2012/6/22
Subject: Contributing to dalvik/libcore: small changes
To: android...@googlegroups.com


We're slightly changing the way we manage some branches, please note
the following changes in the way contributions now work in the dalvik
and libcore projects:

-New contributions to those projects need to be prepared in the
master-dalvik branch. The master branch (and other active development
branches) use a frozen snapshot of those projects, on top of which we
can't accept contributions.

-Existing contributions to those projects (i.e. that have been
uploaded) need no further action.

-If you have a master client, you can switch to master-dalvik with
"repo init -b master-dalvik ; repo sync".

-Technically, you can use master-dalvik to contribute to any project,
but that's not recommended. Unless you're explicitly contributing to
dalvik or libcore, please use the plain master branch to prepare your
contributions.

-Note that, since the master branch uses a frozen snapshot, changes
contributed to the dalvik and libcore projects in master-dalvik don't
get reflected in master.

-This does not affect tagged releases, those will continue to be
managed as usual.

JBQ

--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.

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.
Reply all
Reply to author
Forward
0 new messages