git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
HMHaridas Mahato <haridasmahato12@gmail.com>
Date
Sep 1, 2025, 13:58 UTC
Message-ID
<DCHIM5YWYM7F.1DO69EZ20ONH8@gmail.com>
In-Reply-To
<VI1PR02MB42710CA61134BF19214F855AB304A@VI1PR02MB4271.eurprd02.prod.outlook.com>
On Sun Aug 31, 2025 at 9:43 PM UTC, Skybuck Flying wrote:
Show 6 quoted lines
> 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.
Hello i am new to this kind of mailing (and to os contribution).

If you want to change the procedure from one place to other can you assign this to me (if its still incomplete) and also tell me where can i access this entire code (besides in the thread) so that i can see the live status (like somewhere in the github).

Previous: Skybuck FlyingNext: Skybuck Flying
Message 13 of 15 in “[RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity”
  1. Skybuck FlyingJul 25, 2025
  2. Skybuck FlyingJul 25, 2025
  3. Skybuck FlyingJul 25, 2025
  4. Skybuck FlyingJul 25, 2025
  5. Skybuck FlyingJul 25, 2025
  6. Skybuck FlyingJul 25, 2025
  7. Skybuck FlyingJul 27, 2025
  8. 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 ContinuitySkybuck Flying, Jul 27, 2025
  9. Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow"Skybuck Flying, Aug 29, 2025
  10. Skybuck FlyingAug 29, 2025
  11. Skybuck FlyingAug 31, 2025
  12. Skybuck FlyingAug 31, 2025
  13. Haridas MahatoSep 1, 2025
  14. Skybuck FlyingSep 5, 2025
  15. Skybuck FlyingNov 17, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.