Skip to content

Feature linux tags kernel.org - #441

Open
iam-TJ wants to merge 2 commits into
bootlin:masterfrom
iam-TJ:feature-linux_tags_kernel.org
Open

iam-TJ wants to merge 2 commits into
bootlin:masterfrom
iam-TJ:feature-linux_tags_kernel.org

Conversation

@iam-TJ

@iam-TJ iam-TJ commented Sep 30, 2026

Copy link
Copy Markdown

These two commits add an optional generic git-tag filter argument to update.py and a kernel.org specific filter to projects/linux.sh

I added this specifically to aid indexing local Linux kernel repository that has many remotes and tags that should not be indexed. The generic ability to add git-tag filters can be applied to any project.

Example generic usage:

 update.py 16 v3.?
 update.py 16 "v3.? v3.?? v3.?-rc?"

For Linux specifically:

When the target repository has many remotes other than mainline, stable, and possibly history (i.e. sub-system -next, distro, board support, etc.) there will be many tags that should not be indexed.

Add the special "kernel.org" git-tag filter that will only list mainline, stable, and history tags.

Example Linux usage:

update.py 16 kernel.org

In my case without this filter over 39000 tags were being indexed and required more than 40GiB storage for the indexes for a repository that is only 7.2GiB; with this filter it indexes ~5900 tags.

Accept optional third argument that is one or more git-tag filter
expressions, with more than one surrounded in quote marks and each
filter expression space-separated. E.g:

update.py 16 v3.?
update.py 16 "v3.? v3.?? v3.?-rc?"

This is especially useful where the repository being indexed has
multiple remotes and not all tags should be indexed.

This is a generic facility for any target repository but serves as the
basis for a follow-on commit for Linux project.
When the target repository has many remotes other than mainline,
stable, and possibly history (i.e. sub-system -next, distro, board
support, etc.) there will be many tags that should not be indexed.

Add the special "kernel.org" git-tag filter that will only list
mainline, stable, and history tags.

In my case without this filter over 39000 tags were being indexed and
required more than 40GiB storage for the indexes for a repository that
is only 7.2GiB; with this filter it indexes ~5900 tags.
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

Successfully merging this pull request may close these issues.

1 participant