From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Pavel Rogovoy <p.rogovoy@gmail.com>, git@vger.kernel.org
Subject: Re: Feature Idea: Expanding git to support automatic Semver stamping
Date: Mon, 23 Aug 2021 13:45:12 +0700 [thread overview]
Message-ID: <e478d313-e773-6d83-7d7e-ffce2a4fa0b9@gmail.com> (raw)
In-Reply-To: <CA+NVOTBjgQ60hUZyRcK=igEP5=PSJqUFKf4Z-wYr=7+ESp3Ziw@mail.gmail.com>
On 23/08/21 02.28, Pavel Rogovoy wrote:
> Hi all,
>
> My name is Pavel Rogovoy and I am a git enthusiast. I have developed a
> git-based generic version stamping system that is compliant with the
> Semver standard and I believe it can be integrated into git as a
> sub-command such as git stamp in the form of an external plugin or a
> complete rewrite into git’s source code.
>
I like the idea of automatic semver tagging, especially on case when
developers do releases quickly (with manual tagging, they must know last
tag version in order for the new tag version to be correctly greater
than previous).
> I welcome you to take a look at the stamping utility:
> https://github.com/final-israel/vmn
>
> I will be happy to discuss the main benefits of such a move with you.
> Here are just some:
>
> - Effortless version management and state recovery for single or
> multiple repositories.
If you `git checkout <something>`, you get whatever your code in
<something>'s commit; no need for external tools.
> - Can be used as a convenient git submodule alternative.
I saw "root app" concept [1] in vmn, which is roughly superproject in
git-submodule. But looking at resulting `vmn show`, it more like
metadata for CI job.
When developers clone vmn-ed root app repo, they only get code for root
app only, whereas when they clone normal git repo with submodule, they
can initialize any submodules used and have all history of them on their
fingers.
[1]: https://github.com/final-israel/vmn#root-apps
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2021-08-23 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 19:28 Feature Idea: Expanding git to support automatic Semver stamping Pavel Rogovoy
2021-08-23 6:45 ` Bagas Sanjaya [this message]
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=e478d313-e773-6d83-7d7e-ffce2a4fa0b9@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=p.rogovoy@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).