CIP-dev Archive on lore.kernel.org
 help / color / Atom feed
* [cip-dev] master branch at git.kernel.org/...cip
@ 2021-03-11 12:42 Pavel Machek
  2021-03-15  2:06 ` Nobuhiro Iwamatsu
  0 siblings, 1 reply; 2+ messages in thread
From: Pavel Machek @ 2021-03-11 12:42 UTC (permalink / raw)
  To: Chris.Paterson2, cip-dev

[-- Attachment #1.1: Type: text/plain, Size: 1073 bytes --]

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
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 428 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
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: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [cip-dev] master branch at git.kernel.org/...cip
  2021-03-11 12:42 [cip-dev] master branch at git.kernel.org/...cip Pavel Machek
@ 2021-03-15  2:06 ` Nobuhiro Iwamatsu
  0 siblings, 0 replies; 2+ messages in thread
From: Nobuhiro Iwamatsu @ 2021-03-15  2:06 UTC (permalink / raw)
  To: cip-dev, Chris.Paterson2


[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]

Hi,

> -----Original Message-----
> From: cip-dev@lists.cip-project.org [mailto:cip-dev@lists.cip-project.org] On Behalf Of Pavel Machek
> Sent: Thursday, March 11, 2021 9:43 PM
> To: Chris.Paterson2@renesas.com; cip-dev@lists.cip-project.org
> Subject: [cip-dev] 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).

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

[-- Attachment #2: Type: text/plain, Size: 428 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
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: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-11 12:42 [cip-dev] master branch at git.kernel.org/...cip Pavel Machek
2021-03-15  2:06 ` Nobuhiro Iwamatsu

CIP-dev Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/cip-dev/0 cip-dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 cip-dev cip-dev/ https://lore.kernel.org/cip-dev \
		cip-dev@lists.cip-project.org
	public-inbox-index cip-dev

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.cip-project.lists.cip-dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git