case confusion in branch names

3 views
Skip to first unread message

Gary Ferland

unread,
Nov 12, 2021, 9:42:15 PM11/12/21
to cloudy-dev
I put some effort into creating a message that was lost - this is a test - please ignore

Gary Ferland

unread,
Nov 12, 2021, 9:45:33 PM11/12/21
to cloudy-dev
Screen Shot 2021-11-12 at 9.35.29 PM.pngI created the branch CaseB22 to do the Case B development.  My last commit was 2040ec9b394df3e3b4be7ac50282519a9b9015ec 

Today Fran posted to caseB22 at 6229a00936311140a96497ecffd0cd5a2b7fd5cf.  Note the lower case C.  That commit does not appear in the CaseB22 timeline.  I did a checkoout of the caseB22 branch and both my commits and mine appear to be there.

Gary Ferland

unread,
Nov 12, 2021, 9:47:25 PM11/12/21
to cloudy-dev
given this what should be do?  It is astonishing that git allowed us to get in this mess.  I wonder if it is safe to proceed with Fran's caseB22 or should i merge his change to the CaseB22 branch and delete caseB22?

Gary Ferland

unread,
Nov 12, 2021, 9:49:16 PM11/12/21
to cloudy-dev
cloud9 can deal with the two branches but the mac cannot.  its file system is not case sensitive.

On Friday, November 12, 2021 at 9:42:15 PM UTC-5 Gary Ferland wrote:

Gary Ferland

unread,
Nov 12, 2021, 10:09:42 PM11/12/21
to cloudy-dev
I posted the Hi I CS bugfix to CaseB22.  I am considering removing caseB22
Reply all
Reply to author
Forward
0 new messages