SVN Revision-Like IDs in Git

[Warner Losh]

On Fri, Aug 7, 2020 at 7:28 AM Steve Wills <swills at freebsd.org> wrote:

> Hi,
>
> On 8/6/20 6:01 PM, Sideropoulos, Alexander wrote:
> > Hey folks,
> >
> > According to this page...
> >
> https://hackmd.io/_lvyl1CfTsayB3L0v4fmLA#What%E2%80%99s-with-the-funny-revision-hashes-I-want-revision-numbers
> >
> > ...there are no plans to provide an SVN-revision-like ID for Git commits
> once the switch-over happens.
> >
> > At NetApp, we rely on the SVN revision number to uniquely identify our
> FreeBSD baseline and every cherry-picked patch we apply on top of it. We
> could update all our tooling to accept Git hashes, but this is not a small
> task. And I imagine we are not the only downstream project reliant upon SVN
> revision numbers.
> >
> > Since the SVN revision ID is really just an arbitrary number, has there
> been any thought in simply continuing to manufacture these numbers for Git
> commits going forward? It could even be a post-commit operation where the
> Git notes are updated with a unique (increasing) ID, just as is done today.
> >
> > Thoughts?
>
> I believe there will be git to svn replication for a while, so you could
> possibly continue to use svn until the tooling is updated.
>

Be advised that this svn view may have a different set of r values than the
current repo. Still working out those kinks....

Warner