[OpenWrt-Devel] Including git revision commit hash and svn revision id on release announcement.

[Alive4Ever]

Hello developers.

Probably you are annoyed by people asking which revision is Barrier Breaker
RC3 or similar, because they want to be able to compile the specific release
theirselves.

To address this issue, I think it would be better to add git revision commit
hash for each Openwrt release announcement. So that, if someone already has a
trunk repository, no need to hassle with cloning repository again just for
applying that relase.  Users will be able to go to specific release just by
issuing git revert <git commit hash> or git reset <git commit hash> in their
local git repository.

I hope next release announcement will include git commit hash and svn revision
number for more convenience.
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel