Hey Mike,
Looking at the branch available on github [1], any issues renaming your "arm-dev" branch to "opencsd-bkk16" ? That way there is no ambiguity as to what it is and we can created other branches like "opencsd-[devel, next, stable]" as we move forward.
Tell me what you think, Mathieu
Rename or new branch with the name you want - all about the same in git isn't it?
I'm happy with a re-name, I'll just have to adjust what my tracking branch is pulling from ( and figure out how to adjust what my tracking branch is pulling from)
Regards
Mike
---------------------------------------------------------------- Mike Leach +44 (0)1254 893911 (Direct) Principal Engineer +44 (0)1254 893900 (Main) Arm Blackburn Design Centre +44 (0)1254 893901 (Fax) Belthorn House Walker Rd mailto:mike.leach@arm.com Guide Blackburn BB1 2QE ----------------------------------------------------------------
-----Original Message----- From: Mathieu Poirier [mailto:mathieu.poirier@linaro.org] Sent: 02 March 2016 18:03 To: Mike Leach Cc: coresight@lists.linaro.org Subject: Decoder naming convention on github
Hey Mike,
Looking at the branch available on github [1], any issues renaming your "arm-dev" branch to "opencsd-bkk16" ? That way there is no ambiguity as to what it is and we can created other branches like "opencsd-[devel, next, stable]" as we move forward.
Tell me what you think, Mathieu
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On 03/03/2016, 13:39, "CoreSight on behalf of Mike Leach" <coresight-bounces@lists.linaro.org on behalf of Mike.Leach@arm.com> wrote:
Rename or new branch with the name you want - all about the same in git isn't it?
I'm happy with a re-name, I'll just have to adjust what my tracking branch is pulling from ( and figure out how to adjust what my tracking branch is pulling from)
I think you can just edit .git/config. It¹s all plain text.
‹ Ola
Regards
Mike
Mike Leach +44 (0)1254 893911 (Direct) Principal Engineer +44 (0)1254 893900 (Main) Arm Blackburn Design Centre +44 (0)1254 893901 (Fax) Belthorn House Walker Rd mailto:mike.leach@arm.com Guide Blackburn BB1 2QE
-----Original Message----- From: Mathieu Poirier [mailto:mathieu.poirier@linaro.org] Sent: 02 March 2016 18:03 To: Mike Leach Cc: coresight@lists.linaro.org Subject: Decoder naming convention on github
Hey Mike,
Looking at the branch available on github [1], any issues renaming your "arm-dev" branch to "opencsd-bkk16" ? That way there is no ambiguity as to what it is and we can created other branches like "opencsd-[devel, next, stable]" as we move forward.
Tell me what you think, Mathieu
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ CoreSight mailing list CoreSight@lists.linaro.org https://lists.linaro.org/mailman/listinfo/coresight
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On 3 March 2016 at 05:39, Mike Leach Mike.Leach@arm.com wrote:
Rename or new branch with the name you want - all about the same in git isn't it?
Pretty much yes.
I'm happy with a re-name, I'll just have to adjust what my tracking branch is pulling from ( and figure out how to adjust what my tracking branch is pulling from)
The way I've organised things you won't have to change anything (for now). Two distinct branches have been created [1][2] for people to use - those should not change nor be updated. Let's sit down at Connect to discuss how we will be doing updates from here on.
Mathieu
[1] opencsd-bkk16 ]2] perf-opencsd-4.5-rc6-bkk16
Regards
Mike
Mike Leach +44 (0)1254 893911 (Direct) Principal Engineer +44 (0)1254 893900 (Main) Arm Blackburn Design Centre +44 (0)1254 893901 (Fax) Belthorn House Walker Rd mailto:mike.leach@arm.com Guide Blackburn BB1 2QE
-----Original Message----- From: Mathieu Poirier [mailto:mathieu.poirier@linaro.org] Sent: 02 March 2016 18:03 To: Mike Leach Cc: coresight@lists.linaro.org Subject: Decoder naming convention on github
Hey Mike,
Looking at the branch available on github [1], any issues renaming your "arm-dev" branch to "opencsd-bkk16" ? That way there is no ambiguity as to what it is and we can created other branches like "opencsd-[devel, next, stable]" as we move forward.
Tell me what you think, Mathieu
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
-
Mathieu Poirier -
Mike Leach -
Ola Liljedahl