Date: Fri, 7 Aug 2020 09:27:56 -0400 From: Steve Wills <swills@FreeBSD.org> To: "Sideropoulos, Alexander" <Alexander.Sideropoulos@netapp.com>, "freebsd-git@freebsd.org" <freebsd-git@freebsd.org> Cc: "Maxwell, Larus" <Larus.Maxwell@netapp.com> Subject: Re: SVN Revision-Like IDs in Git Message-ID: <1c82b615-6685-ec20-c6da-6e76035b3ef4@FreeBSD.org> In-Reply-To: <013F16E7-DDBB-4C2F-829D-D08B53CC7585@netapp.com> References: <013F16E7-DDBB-4C2F-829D-D08B53CC7585@netapp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1c82b615-6685-ec20-c6da-6e76035b3ef4>