You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`(option-1|option-2)` -> You *must* provide either a value for `option-1` or `option-2`.
48
48
-`[option]` -> You *may* provide a value
49
49
50
-
The script must be provided with `busybox` or `linux` as first argument, in order to specify which SPL should be considered.
50
+
The script must be provided with `busybox`, `linux`, or the https clone link of a public git repository as first argument, in order to specify which SPL should be considered.
51
51
In addition, you can optionally provide either one or two more arguments specifying a commit-id or git-tag.
52
52
53
-
If you specify __no__ id or tag, the entire history is considered.
53
+
> If you specify `linux` or `busybox`, a full extraction, including the analysis of the build system, will be performed for either Linux or BusyBox. If you specify the clone link to a git repository, a partial extraction, without considering the build system, will be performed. This is due to technicalities of the build system analysis, which require a project specific setup, which we only performed for Linux and BusyBox.
54
54
55
-
If you specify __exactly one__ id or tag, the extraction will only consider the one commit that is found under the id/tag.
55
+
> If you specify __no__ id or tag, the entire history is considered.
56
+
57
+
> If you specify __exactly one__ id or tag, the extraction will only consider the one commit that is found under the id/tag.
56
58
This can be used to quickly test whether everything is working as intended or to run the extraction for one commit only (e.g., when no evolution information is necessary).
57
59
58
-
If you specify __two__ ids or tags, the extraction will consider the range of commits that lies between the first and the second
60
+
> If you specify __two__ ids or tags, the extraction will consider the range of commits that lies between the first and the second
59
61
commit. The commit retrieval follows the same logic as [git log](https://git-scm.com/docs/git-log), i.e., it will retrieve
60
62
all commits that are ancestors of the second commit, but __not__ ancestors of the first commit.
0 commit comments