On Mon, Jul 03, 2017 at 09:08:08AM +0100, Milosz Wasilewski wrote:
On 23 June 2017 at 12:22, Mark Brown broonie@kernel.org wrote:
On Wed, Jun 21, 2017 at 09:48:41PM +0100, Milosz Wasilewski wrote:
On 21 June 2017 at 15:42, Mark Brown broonie@kernel.org wrote:
On Wed, Jun 21, 2017 at 12:03:01PM +0000, Linaro QA wrote:
kernel-describe: 8853995
This looks like it's taken a step backwards?
I'll check but I think this is how it works on this tree.
Really, no. *All* kernels should end up with something based off a tag.
milosz@milosz-tp:~/linaro/oe/hikey-linaro$ git remote -v origin https://android.googlesource.com/kernel/hikey-linaro (fetch) origin https://android.googlesource.com/kernel/hikey-linaro (push) milosz@milosz-tp:~/linaro/oe/hikey-linaro$ git branch
- android-hikey-linaro-4.4 android-hikey-linaro-4.9 master
milosz@milosz-tp:~/linaro/oe/hikey-linaro$ git describe --always 6b116e0f
and 4.9
milosz@milosz-tp:~/linaro/oe/hikey-linaro$ git branch android-hikey-linaro-4.4
- android-hikey-linaro-4.9 master
milosz@milosz-tp:~/linaro/oe/hikey-linaro$ git describe --always db724a5
Anything I'm doing wrong?
Do you not have the upstream branch that contains the git tags for the releases? You will need that.
Also, you might need to use 'git describe --contains', that's what I always use otherwise the output can be "odd" if you don't know exactly what you are looking at...
thanks,
greg k-h