Hi,
How can I find which commits entered a certain MediaWiki "build" (especially the -wmfX ones). Are there any tags in the repository or is there a page that holds that information?
Thanks, Strainu
There's branches for the current versions and tags for the older ones. Clone mediawiki/core and git tag and git branch -r will show them.
-Chad On Jan 6, 2014 8:47 AM, "Strainu" strainu10@gmail.com wrote:
Hi,
How can I find which commits entered a certain MediaWiki "build" (especially the -wmfX ones). Are there any tags in the repository or is there a page that holds that information?
Thanks, Strainu
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
And to check a specific commit easier, expand the "Included in" section on its Gerrit page.
-Liangent
On Tue, Jan 7, 2014 at 12:58 AM, Chad innocentkiller@gmail.com wrote:
There's branches for the current versions and tags for the older ones. Clone mediawiki/core and git tag and git branch -r will show them.
-Chad On Jan 6, 2014 8:47 AM, "Strainu" strainu10@gmail.com wrote:
Hi,
How can I find which commits entered a certain MediaWiki "build" (especially the -wmfX ones). Are there any tags in the repository or is there a page that holds that information?
Thanks, Strainu
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
(anonymous) wrote:
How can I find which commits entered a certain MediaWiki "build" (especially the -wmfX ones). Are there any tags in the repository or is there a page that holds that information?
Gerrit lists remote branches for -wmf:
| [tim@passepartout ~/public_html/w]$ git branch -r | fgrep wmf/1.23 | gerrit/wmf/1.23wmf1 | gerrit/wmf/1.23wmf2 | gerrit/wmf/1.23wmf3 | gerrit/wmf/1.23wmf4 | gerrit/wmf/1.23wmf5 | gerrit/wmf/1.23wmf6 | gerrit/wmf/1.23wmf7 | gerrit/wmf/1.23wmf8 | gerrit/wmf/1.23wmf9 | [tim@passepartout ~/public_html/w]$
For the other way (you have a commit and want to know where it's coming from), in the general case, Git has a neat fea- ture: "git describe --tags" will traverse the tree upwards and produce an identifier with the SHA1, the "nearest" tag and the number of steps between; however, with current mas- ter:
| [tim@passepartout ~/public_html/w]$ git describe --tags | 1.6.0-44845-g1e5e4d9 | [tim@passepartout ~/public_html/w]$
So Git had to travel 44845 nodes to find a tag -- which is useless :-).
Tim
wikitech-l@lists.wikimedia.org