master branch at git.kernel.org/...cip
Hi!
Chris pointed out our master branch at git.kernel.org is rather old:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/refs/heads
master CIP: Bump version suffix to -cip28 after Renesas patches Ben Hutchings 2 years
Master branch is really not too applicable for our workflow. Yes, 2 years old version of 4.4 looks out of place.
I see these options:
1) leave it alone. (+) It is quite obvious development is not happening there (-) It looks strange.
2) delete it. (-) I'm not sure that is possible or what problems it might cause.
3) update it to Linus' 5.12-rc1 and keep it updated. (-) Extra work to keep it updated, (-) we don't really do anything with mainline commits newer than 5.10
4) update it to Linus' 5.10, and only touch it when the linux-5.21-cip is branched out.
Any other ideas?
My preference would be (1) and (4).
Best regards,
Pavel
Signature · 2 lines
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6276): https://lists.cip-project.org/g/cip-dev/message/6276
Mute This Topic: https://lists.cip-project.org/mt/81251519/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Hi,
Quoted 30 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Pavel Machek
Sent: Thursday, March 11, 2021 9:43 PM
To: [email protected]; [email protected]
Subject: [cip-dev] master branch at git.kernel.org/...cipHi!
Chris pointed out our master branch at git.kernel.org is rather old:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/refs/heads
master CIP: Bump version suffix to -cip28 after Renesas patches Ben Hutchings 2 years
Master branch is really not too applicable for our workflow. Yes, 2 years old version of 4.4 looks out of place.
I see these options:
1) leave it alone. (+) It is quite obvious development is not happening there (-) It looks strange.
2) delete it. (-) I'm not sure that is possible or what problems it might cause.
3) update it to Linus' 5.12-rc1 and keep it updated. (-) Extra work to keep it updated, (-) we don't really do anything with mainline commits newer than 5.10
Quoted 6 lines
4) update it to Linus' 5.10, and only touch it when the linux-5.21-cip is branched out.
Any other ideas?
My preference would be (1) and (4).
I want to choose 1 or 3.
We have multiple release branches, so setting the branch that manages a particular version to the master branch can be a bit confusing. How about managing a branch similar to LTS tree?
Best regards,
Nobuhiro
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6280): https://lists.cip-project.org/g/cip-dev/message/6280
Mute This Topic: https://lists.cip-project.org/mt/81251519/4520388
Group Owner: [email protected]
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388/727948398/xyzzy [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-