On 18/11/13 12:03 , "Dong, Junfeng" <[email protected]<mailto:[email protected]>> wrote:
Hi release engineer team, What are the following branches name accepted/tizen/*/* for? Many packages are created such branch recently. I list some examples. Should the maintainer update them? Since they are different for each git tree, what is the rule of creating them? Those special branches supposed to point to state of the code that is inside corresponding project. Tizen:Mobile -> accepted/tizen/mobile Developers should not touch those branches, those are created and updated automatically by build system. They are useful for example in manifest files, where you can change that default head is not “most recent” code, but “most recent released and accepted code”. gcc48> git branch -a * tizen remotes/origin/HEAD -> origin/tizen remotes/origin/accepted/tizen/ivi remotes/origin/accepted/tizen/mobile qemu-accel> git branch -a master * tizen tmp remotes/origin/HEAD -> origin/master remotes/origin/accepted/tizen/ivi/release remotes/origin/accepted/tizen/mobile remotes/origin/master remotes/origin/tizen qemu> git branch -a * tizen upstream remotes/origin/HEAD -> origin/tizen remotes/origin/accepted/tizen/ivi/stable remotes/origin/pristine-tar remotes/origin/tizen remotes/origin/tizen_ivi_stable remotes/origin/upstream Best Regards Junfeng -- Best regards, Alexander Kanevskiy. --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
