Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "git@xxxxxxxxxxxxxxx" <git@xxxxxxxxxxxxxxx>
Subject: Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow"
From: Skybuck Flying <skybuck2000@xxxxxxxxxxx>
Date: Sun, 31 Aug 2025 21:43:23 +0000
Accept-language: en-US
In-reply-to: <VI1PR02MB4271CE7B8F32225C98A2DCBEB33AA@VI1PR02MB4271.eurprd02.prod.outlook.com>
Msip_labels:
References: <DB7PR02MB4265BF28A39C7BD3DB097E1CB359A@DB7PR02MB4265.eurprd02.prod.outlook.com> <DB7PR02MB4265499C1103242CB482B407B359A@DB7PR02MB4265.eurprd02.prod.outlook.com> <DB7PR02MB4265CDBD131FB755B0799B2FB359A@DB7PR02MB4265.eurprd02.prod.outlook.com> <DB7PR02MB42655790BB6E1EF589B7D173B359A@DB7PR02MB4265.eurprd02.prod.outlook.com> <DB7PR02MB4265DDA928244F526CF1EF4AB359A@DB7PR02MB4265.eurprd02.prod.outlook.com> <DB7PR02MB4265527016FB04A500FBE321B35BA@DB7PR02MB4265.eurprd02.prod.outlook.com> <VI1PR02MB42713B3BBD5802512B5FC9FBB33AA@VI1PR02MB4271.eurprd02.prod.outlook.com> <VI1PR02MB4271CE7B8F32225C98A2DCBEB33AA@VI1PR02MB4271.eurprd02.prod.outlook.com>
Thread-index: AQHcGR0afBR4UVFtH0y7jlWzQ0OEhLR6DyAsgAM/ILI=
Thread-topic: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow"

Little bug fix is possible:

Copy & Paste the procedure GetNextContributionNumber from git-new-contribution.dpr to git-back-to.dpr to make git-base-to use a correctly incremented contribution number.

Bye for now,
  Skybuck.

Follow-Ups:
- Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow"
  - From: Skybuck Flying

References:
- [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity
  - From: Skybuck Flying
- Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity
  - From: Skybuck Flying
- Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity
  - From: Skybuck Flying
- Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity
  - From: Skybuck Flying
- Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity
  - From: Skybuck Flying
- Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity
  - From: Skybuck Flying
- Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow"
  - From: Skybuck Flying
- Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow"
  - From: Skybuck Flying

Prev by Date: Re: [PATCH v2 0/8] sparse-checkout: add 'clean' command
Next by Date: Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow"
Previous by thread: Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow"
Next by thread: Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow"
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]