On Thu, 25 Jan 2018, Michael Stapelberg wrote: > > or (since upstream is somewhat redundant): > > I don’t feel that “upstream” is redundant. I think the contents of a branch > should be obvious from the name.
Ack. > The “pristine” namespace could easily be confused with “pristine-tar”, so > I’d prefer avoiding that name altogether if possible. Ack, as well. > > this would also allow to retain upstream/ with the original meaning for > > Wait, now I’m confused. Isn’t “upstream” the same as “upstream/latest”? > What “original meaning” are you referring to? :) I'm also confused. On Fri, 26 Jan 2018, Michael Stapelberg wrote: > One thing came up during the implementation to which I’d like your > feedback: if the upstream branch isn’t by chance already tagged with a > proper version number (e.g. v1.2), how do we get a suitable version number > for the git snapshot we’re about to package? We have such logic in > dh-make-golang: > https://github.com/Debian/dh-make-golang/blob/5a5180dce36c9c878b7551640ff018a6dfabf0dd/version.go#L19 > — as you can see it’s rather complicated. I couldn’t find anything > comparable in git-buildpackage yet. Did I miss it? If no, could such logic > be added? I don't know what's available in git-buildpackage but if it's not, then I think it's OK to add something like this. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
