From: "Haridas Mahato" <haridasmahato12@gmail•com>
To: "Skybuck Flying" <skybuck2000@hotmail•com>,
"git@vger•kernel.org" <git@vger•kernel.org>
Subject: Re: Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow"
Date: Mon, 01 Sep 2025 13:58:07 +0000 [thread overview]
Message-ID: <DCHIM5YWYM7F.1DO69EZ20ONH8@gmail.com> (raw)
In-Reply-To: <VI1PR02MB42710CA61134BF19214F855AB304A@VI1PR02MB4271.eurprd02.prod.outlook.com>
On Sun Aug 31, 2025 at 9:43 PM UTC, Skybuck Flying wrote:
> 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).
next prev parent reply other threads:[~2025-09-01 13:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 18:53 [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity Skybuck Flying
2025-07-25 19:05 ` Skybuck Flying
2025-07-25 19:20 ` Skybuck Flying
2025-07-25 19:24 ` Skybuck Flying
2025-07-25 20:21 ` Skybuck Flying
2025-07-25 20:38 ` Skybuck Flying
2025-07-27 3:04 ` Skybuck Flying
2025-07-27 23:55 ` SuperLaserC from LaserA and LaserB, continue LaserA/B fresh from SuperLaserC was " Skybuck Flying
2025-08-29 19:42 ` Was "Re: [RFC] Proposed Git Workflow for Permanent History, Explicit Branch Status, and Developer Continuity" now "Skybuck's GitFlow" Skybuck Flying
2025-08-29 20:11 ` Skybuck Flying
2025-08-31 21:43 ` Skybuck Flying
2025-08-31 22:23 ` Skybuck Flying
[not found] ` <AM0PR02MB4450BE9364544EE7ECE2CE13B3C9A@AM0PR02MB4450.eurprd02.prod.outlook.com>
2025-11-17 14:37 ` Skybuck Flying
2025-09-01 13:58 ` Haridas Mahato [this message]
2025-09-05 8:31 ` Skybuck Flying
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=DCHIM5YWYM7F.1DO69EZ20ONH8@gmail.com \
--to=haridasmahato12@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=skybuck2000@hotmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox