Closed taskset closed 5 years ago
Sorry, I'm not really getting the point of this.
julia
On Thu, 8 Nov 2018, Wen Yang wrote:
According to linux's devel git repository and stable repository, the commit label is automatically generated.
For example, a commit in the Linux devel repository: Commit b248371628aad599a48540962f6b85a21a8a0c3f Author: Takashi Iwai tiwai@suse.de Date: Sun Jan 31 10:32:37 2016 +0100
ALSA: pcm: Fix potential deadlock in OSS emulation
It corresponds to the commit in the origin/linux-2.6.33.y branch of the stable repository: Commit 937524d03c6eaf3a5d00b714eaaf15a1a9c8478a Author: Takashi Iwai tiwai@suse.de Date: Sun Jan 31 10:32:37 2016 +0100
ALSA: pcm: Fix potential deadlock in OSS emulation
Commit b248371628aad599a48540962f6b85a21a8a0c3f upstream.
We based on the keywords in the commit log of a branch in the stable repository: Commit b248371628aad599a48540962f6b85a21a8a0c3f upstream, to determine whether it should be marked with a stable label.
You can view, comment on, or merge this pull request online at:
https://github.com/hvdthong/PatchNetTool/pull/2
Commit Summary
adding generate_labelled_commits.sh
File Changes
A preprocessing/generate_labelled_commits.sh (91)
Patch Links:
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.[AAesmn0UMT2nrcmRPNpcSDJ6VkMZoNyIks5utTHHgaJpZM4YWGiY.gif]
Hi @JuliaLawall , Thanks for your feedback We want to be able to automatically generate a stable or stable label based on linux's devel git repository and stable repository. We use it like this: $ bash -x generate_labelled_commits.sh -b 2016-02-01 -e 2016-02-02 -d /path/to/linux/devel/git_repo -s /path/to/linux/stable/git_repo -r liux-stable-branch(eg:origin/linux-2.6.33.y) -o ./commit_list( list of labelled commits)
finally, we can see the list of labelled commits in the commit_list file: $ cat commit_list | more f9e37c683c8a0a2a200181dab2b784a126e0b106: false 007270f136858ec880e2f2c6bfbdd489aae2bf56: false 26e30c6489f4774492c168c7b953e575a16765f7: false ...... cc85f7a634cfaf9f0713c6aa06d08817424db37a: true 2d1b5c08366acd46c35a2e9aba5d650cb5bf5c19: true 4c7cad4bbf718e73a49e236e2b79489f1ee83810: false .....
Thanks. Regards,
We've fixed some bugs and will submit a new version. Thank you.
According to linux's devel git repository and stable repository, the commit label is automatically generated.
For example, a commit in the Linux devel repository: Commit b248371628aad599a48540962f6b85a21a8a0c3f Author: Takashi Iwai tiwai@suse.de Date: Sun Jan 31 10:32:37 2016 +0100
It corresponds to the commit in the origin/linux-2.6.33.y branch of the stable repository: Commit 937524d03c6eaf3a5d00b714eaaf15a1a9c8478a Author: Takashi Iwai tiwai@suse.de Date: Sun Jan 31 10:32:37 2016 +0100
We based on the keywords in the commit log of a branch in the stable repository: Commit b248371628aad599a48540962f6b85a21a8a0c3f upstream, to determine whether it should be marked with a stable label.