CIP-dev Archive on lore.kernel.org
 help / color / Atom feed
From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <cip-dev@lists.cip-project.org>, <Chris.Paterson2@renesas.com>
Subject: Re: [cip-dev] master branch at git.kernel.org/...cip
Date: Mon, 15 Mar 2021 02:06:39 +0000
Message-ID: <OSBPR01MB29837731DA0D7EA8C45D17F5926C9@OSBPR01MB2983.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20210311124248.GB32725@amd>


[-- 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]
-=-=-=-=-=-=-=-=-=-=-=-


      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 12:42 Pavel Machek
2021-03-15  2:06 ` Nobuhiro Iwamatsu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OSBPR01MB29837731DA0D7EA8C45D17F5926C9@OSBPR01MB2983.jpnprd01.prod.outlook.com \
    --to=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=Chris.Paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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