Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #84524 > unrolled thread

PSA: Renaming branches in kernel-team repositories

Started byBen Hutchings <ben@decadent.org.uk>
First post2024-11-13 22:40 +0100
Last post2024-11-24 12:50 +0100
Articles 5 — 2 participants

Back to article view | Back to linux.debian.kernel


Contents

  PSA: Renaming branches in kernel-team repositories Ben Hutchings <ben@decadent.org.uk> - 2024-11-13 22:40 +0100
    Re: PSA: Renaming branches in kernel-team repositories Luca Boccassi <bluca@debian.org> - 2024-11-13 22:50 +0100
      Re: PSA: Renaming branches in kernel-team repositories Ben Hutchings <ben@decadent.org.uk> - 2024-11-14 00:10 +0100
    Re: PSA: Renaming branches in kernel-team repositories Ben Hutchings <ben@decadent.org.uk> - 2024-11-24 01:50 +0100
      Re: PSA: Renaming branches in kernel-team repositories Luca Boccassi <bluca@debian.org> - 2024-11-24 12:50 +0100

#84524 — PSA: Renaming branches in kernel-team repositories

FromBen Hutchings <ben@decadent.org.uk>
Date2024-11-13 22:40 +0100
SubjectPSA: Renaming branches in kernel-team repositories
Message-ID<JItfH-8I9Q-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Following the branch renaming in the linux repository and discussion in
today's team meeting, I want to rename branches in other kernel-team
package repositories to follow DEP-14.

For iproute2, I plan to rename "debian/sid" to "debian/unstable" and
the other suite branches to have a "debian/" prefix.

For the following repositories, I plan to rename "master" to
"debian/latest" and the suite branches to have a "debian/" prefix:

- ethtool
- firmware-free
- firmware-nonfree
- initramfs-tools
- kernel-handbook
- klibc
- kup
- linux-base
- nfs-utils
- wireless-regdb

I believe the other package repositories are already following DEP-14.

I will wait at least a week before doing anything, in case there are
objections to the above plan.

Ben.

-- 
Ben Hutchings
One of the nice things about standards is that
there are so many of them.

[toc] | [next] | [standalone]


#84526

FromLuca Boccassi <bluca@debian.org>
Date2024-11-13 22:50 +0100
Message-ID<JItpn-8Idf-7@gated-at.bofh.it>
In reply to#84524
On Wed, 13 Nov 2024 at 21:20, Ben Hutchings <ben@decadent.org.uk> wrote:
>
> Following the branch renaming in the linux repository and discussion in
> today's team meeting, I want to rename branches in other kernel-team
> package repositories to follow DEP-14.
>
> For iproute2, I plan to rename "debian/sid" to "debian/unstable" and
> the other suite branches to have a "debian/" prefix.

The only active branch apart from debian/sid is
debian/bookworm-backports, which already has the prefix. If you want
to duplicate the stale branches to add debian/ prefix there that
sounds fine, but it's unlikely they are going to see any activity,
doesn't hurt I guess, branches are cheap, and the debian/ prefix makes
sense to namespace them, so not a problem.
However, I'm not sure about sid -> unstable? What's the reason for
that? It's a lot of churn to change everything and everyone given it's
the main branch where I merge things and do all the work?

[toc] | [prev] | [next] | [standalone]


#84530

FromBen Hutchings <ben@decadent.org.uk>
Date2024-11-14 00:10 +0100
Message-ID<JIuEN-8Jdz-5@gated-at.bofh.it>
In reply to#84526

[Multipart message — attachments visible in raw view] — view raw

On Wed, 2024-11-13 at 21:26 +0000, Luca Boccassi wrote:
> On Wed, 13 Nov 2024 at 21:20, Ben Hutchings <ben@decadent.org.uk> wrote:
> > 
> > Following the branch renaming in the linux repository and discussion in
> > today's team meeting, I want to rename branches in other kernel-team
> > package repositories to follow DEP-14.
> > 
> > For iproute2, I plan to rename "debian/sid" to "debian/unstable" and
> > the other suite branches to have a "debian/" prefix.
> 
> The only active branch apart from debian/sid is
> debian/bookworm-backports, which already has the prefix. If you want
> to duplicate the stale branches to add debian/ prefix there that
> sounds fine, but it's unlikely they are going to see any activity,
> doesn't hurt I guess, branches are cheap, and the debian/ prefix makes
> sense to namespace them, so not a problem.
> However, I'm not sure about sid -> unstable? What's the reason for
> that? It's a lot of churn to change everything and everyone given it's
> the main branch where I merge things and do all the work?

The reason is that DEP-14 specifically mentions "debian/unstable"
instead of "debian/sid", so that's what other developers are going to
expect to see.

I realise all this renaming will be disruptive, but it moves us toward
a more consistent experience for developers working across the kernel
team packages and across the whole distribution.

Ben.

-- 
Ben Hutchings
One of the nice things about standards is that
there are so many of them.

[toc] | [prev] | [next] | [standalone]


#84644

FromBen Hutchings <ben@decadent.org.uk>
Date2024-11-24 01:50 +0100
Message-ID<JM8Z3-b7L1-3@gated-at.bofh.it>
In reply to#84524

[Multipart message — attachments visible in raw view] — view raw

I will go ahead with this on Monday, possibly excluding the debian/sid
renaming in iproute2.

Ben.

On Wed, 2024-11-13 at 22:20 +0100, Ben Hutchings wrote:
> Following the branch renaming in the linux repository and discussion in
> today's team meeting, I want to rename branches in other kernel-team
> package repositories to follow DEP-14.
> 
> For iproute2, I plan to rename "debian/sid" to "debian/unstable" and
> the other suite branches to have a "debian/" prefix.
> 
> For the following repositories, I plan to rename "master" to
> "debian/latest" and the suite branches to have a "debian/" prefix:
> 
> - ethtool
> - firmware-free
> - firmware-nonfree
> - initramfs-tools
> - kernel-handbook
> - klibc
> - kup
> - linux-base
> - nfs-utils
> - wireless-regdb
> 
> I believe the other package repositories are already following DEP-14.
> 
> I will wait at least a week before doing anything, in case there are
> objections to the above plan.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable
from a rigged demo.

[toc] | [prev] | [next] | [standalone]


#84650

FromLuca Boccassi <bluca@debian.org>
Date2024-11-24 12:50 +0100
Message-ID<JMjhL-bea2-1@gated-at.bofh.it>
In reply to#84644
I've just pushed the new branches and switched the defaults myself.

On Sun, 24 Nov 2024 at 00:30, Ben Hutchings <ben@decadent.org.uk> wrote:
>
> I will go ahead with this on Monday, possibly excluding the debian/sid
> renaming in iproute2.
>
> Ben.
>
> On Wed, 2024-11-13 at 22:20 +0100, Ben Hutchings wrote:
> > Following the branch renaming in the linux repository and discussion in
> > today's team meeting, I want to rename branches in other kernel-team
> > package repositories to follow DEP-14.
> >
> > For iproute2, I plan to rename "debian/sid" to "debian/unstable" and
> > the other suite branches to have a "debian/" prefix.
> >
> > For the following repositories, I plan to rename "master" to
> > "debian/latest" and the suite branches to have a "debian/" prefix:
> >
> > - ethtool
> > - firmware-free
> > - firmware-nonfree
> > - initramfs-tools
> > - kernel-handbook
> > - klibc
> > - kup
> > - linux-base
> > - nfs-utils
> > - wireless-regdb
> >
> > I believe the other package repositories are already following DEP-14.
> >
> > I will wait at least a week before doing anything, in case there are
> > objections to the above plan.
>
> --
> Ben Hutchings
> Any smoothly functioning technology is indistinguishable
> from a rigged demo.
>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web