On Mon, 12 Oct 2015, Felix Fietkau wrote:
On 2015-10-12 22:36, David Lang wrote:
On Mon, 12 Oct 2015, Felix Fietkau wrote:
On 2015-10-12 22:28, David Lang wrote:
On Mon, 12 Oct 2015, Felix Fietkau wrote:
On 2015-10-12 22:02, Javier Domingo Cansino wrote:
Would it be possible to track the revision number in an automated
way even in a git repo? So store the r number, and automatically
increment on commits. Not sure if that's an option, but it seems
like it might address the problem.
In git you wouldn't need such thing, the way would be to track the
forking point comparing the user history with the upstream master
history, and describing the path. The oneliner I sent before (which I
now realize I split in two), did (or will do) the following.
1) Go back in history and find the latest tag, save it as $tag
We currently don't have any tags for mainline trunk, since we usually
don't directly release from it.
I would put a nightly tag in place (tags are pretty cheap)
Sounds nasty.
why?
If we want to tag minor releases, the real release tags get hidden
behind an ever growing amount of auto-generated tag spam.
If you tag weekly there aren't that many tags, and you can give the auto-weekly
tags a different format than releases
v15.05 release
a15.40 weekly tag for week 40 of 2015
these will even sort so the auto tags will scroll off the top and what you care
about will be at the end of the list :-)
David Lang
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
