on Mon Oct 21 2013, "Niall Douglas"
On 20 Oct 2013 at 20:40, Dave Abrahams wrote:
git lets you create arbitrary refs to arbitrary SHAs, so there is absolutely nothing stopping Boost2Git filling a directory of SHA refs named after each SVN revision e.g. refs/svnrefs/12345 => abcdef...
Neat, but I wonder if we really want to create eighty thousand refs for this purpose.
You don't need to include them into the default refs fetch spec i.e. a standard clone won't contain them, but a fetch with the right fetch spec will.
I know.
In other words, they only consume disc space and bandwidth for those who ask for them.
Won't they appear in GitHub's menu and/or network graph?
Even then, I'd assume such refs would end up in packed-refs anyway, and so would be highly efficient.
Not that I mind doing this; it'd be a fairly simple change to the tool, but we can always create these afterwards, FWIW, since the revnum is now contained in the commit message. -- Dave Abrahams