Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit... | git

[RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity · Skybuck Flying <hidden> · 2025-07-25
Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity · Skybuck Flying <hidden> · 2025-07-25
Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity · Skybuck Flying <hidden> · 2025-07-25
Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity · Skybuck Flying <hidden> · 2025-07-25
Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity · Skybuck Flying <hidden> · 2025-07-25
Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity · Skybuck Flying <hidden> · 2025-07-25
Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity · Skybuck Flying <hidden> · 2025-07-27
SuperLaserC from LaserA and LaserB, continue LaserA/B fresh from SuperLaserC was Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity · Skybuck Flying <hidden> · 2025-07-27
Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow" · Skybuck Flying <hidden> · 2025-08-29
Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow" · Skybuck Flying <hidden> · 2025-08-29
Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow" · Skybuck Flying <hidden> · 2025-08-31
Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow" · Skybuck Flying <hidden> · 2025-08-31
Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow" · Haridas Mahato <hidden> · 2025-09-01
Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow" · Skybuck Flying <hidden> · 2025-09-05

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

From: Skybuck Flying <hidden>
Date: 2025-08-31 21:43:25

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.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help