Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

git tag 4.9.27-ti-r33 missing #126

Closed
floion opened this issue Jun 9, 2017 · 6 comments
Closed

git tag 4.9.27-ti-r33 missing #126

floion opened this issue Jun 9, 2017 · 6 comments

Comments

@floion
Copy link

floion commented Jun 9, 2017

Hi,
I noticed tag 4.9.27-ti-r33 is missing. Was there an issue with that particular tag or are these tags moving targets and we should not rely on using them?

@RobertCNelson
Copy link
Member

@floion not sure what happened on that one.. As May 8th, 2017 was a monday.. So i can't blame it on forgetting to push on a weekend. Looks like just got distracted at day job.

For backup, you can always grab the same tag from this repo:

https://github.com/RobertCNelson/linux-stable-rcn-ee

Which actually pre-dates the beagleboard repo, and has almost every tag i've ever released:

https://github.com/RobertCNelson/linux-stable-rcn-ee/tree/4.9.27-ti-r33

^note, since there are over 4K tag's github's web gui just can't handle the list, so you need to manually put the tag after "./tree/"

the other difference between the beagleboard repo, the reference config is named differently:

rcn-ee_defconfig instead of bb.org_defconfig

This is because my kernel *.deb build farm, uses https://github.com/RobertCNelson/linux-stable-rcn-ee/ directly when building the final *.deb's..

Regards,

@RobertCNelson
Copy link
Member

@floion just another quick note for reference. ;)

Pushing to https://github.com/beagleboard/linux/ is manual, (so if i forget or get distracted, it'll happen)

Where as pushing to https://github.com/RobertCNelson/linux-stable-rcn-ee/ is automated and the "only" way my build farm will kick off a kernel *.deb build..

Regards,

@floion
Copy link
Author

floion commented Jun 9, 2017

Thanks for the explanation.
Let me also clarify: tag 4.9.27-ti-r33 used to exist and now it does not exist anymore.
It's not a big deal that this particular tag is missing now, I was just wondering if these tags are supposed to be volatile or we can safely rely on them in the future.

@RobertCNelson
Copy link
Member

@floion oh, that's not normal.. I don't delete any of the pushed tag's.. I'm cloning the linux repo right now, to see if we lost all, or just some are broken..

Regards,

@RobertCNelson
Copy link
Member

RobertCNelson commented Jun 9, 2017

@floion

weird:

voodoo@hades:/mnt/data/data/repo/linux$ cat .git/config 
[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
[remote "origin"]
	url = https://github.com/beagleboard/linux
	fetch = +refs/heads/*:refs/remotes/origin/*
[branch "4.4"]
	remote = origin
	merge = refs/heads/4.4
voodoo@hades:/mnt/data/data/repo/linux$ git tag --list | grep 4.9.27
4.9.27-ti-r33
4.9.27-ti-rt-r33

the weblink works:

https://github.com/beagleboard/linux/tree/4.9.27-ti-r33

must have been a github web crash/issue/etc...

Regards,

@floion
Copy link
Author

floion commented Jun 10, 2017

Yeah, it seems to be okay now.
Thanks for looking at this.

@floion floion closed this as completed Jun 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants