Hi, Guido: Last year there was discussion of creating gbp-config as a separate package and allowing it to be used to query the gbp config to fetch the upstream import tag format. Is that still on the roadmap? Or should tools that depend on this implement their own logic to figure out the tag name (i.e. use the default value `upstream/%s` or read debian/gbp.conf to see if it was customized)?
Now that pristine-tar is supported, I tried to start using tag2upload again and noticed the user experience for git-buildpackage uploads is still the exact same as a year ago, and git-debpush (based on git-deborig) does not know that the upstream tarball was imported on upstream/1.4.5 despite the tag name following usual git-buildpackage convention: ± git-debpush --gbp git-debpush: found upstream tags: v1.4.5 upstream/1.4.5 git-debpush: use --upstream=TAG to say which one to use
