How to trace a specific historic file in the Linux kernel tree: Git question
Clash Royale CLAN TAG#URR8PPP
I'm currently manually building a Linux image with some specific drivers for a Xilinx Zynqmp device. Aside from the main Linux tree, there are 2 other mirrored Linux repositories, one from Xilinx and another where the driver was developed with.
I noticed some differences within the source files. I know about the "git blame" function and it tells me it is an older Xilinx developed file which was being used for the driver development.
My Question:
How do I track down the exact source file where the driver was build on? I would like to know which branch or tag was cloned/merged in order to build the driver. Because logically the driver developers kernel leaps behind the Xilinx dev kernel. How do I do this?
Any other git tips & tricks in this matter are very much welcome.
linux drivers git source trace
asked Jan 4 at 8:37
J. DoeJ. Doe
1
add a comment |
I'm currently manually building a Linux image with some specific drivers for a Xilinx Zynqmp device. Aside from the main Linux tree, there are 2 other mirrored Linux repositories, one from Xilinx and another where the driver was developed with.
I noticed some differences within the source files. I know about the "git blame" function and it tells me it is an older Xilinx developed file which was being used for the driver development.
My Question:
How do I track down the exact source file where the driver was build on? I would like to know which branch or tag was cloned/merged in order to build the driver. Because logically the driver developers kernel leaps behind the Xilinx dev kernel. How do I do this?
Any other git tips & tricks in this matter are very much welcome.
linux drivers git source trace
asked Jan 4 at 8:37
J. DoeJ. Doe
1
I am not sure to understand exactly your need, maybe you should add details on the specific git repository you are looking at, the files you are interested in, and what commands you tried already. As for tips and tricks, the following commands besidesgit blamecan be useful to do searches:git log -S,git log -Gandgit bisect.
– Patrick Mevzek
Jan 6 at 21:17
@PatrickMevzek I know the question is a bit vague. I have this driver from Analog Devices and they claim the Xilinx linux repo get's merged periodically with theirs. But it is very unclear to me which branch or tag was used as a base for their driver. I am looking for some tricks or tools to navigate through the giant Linux repository and track down what items the driver authors changed or not.
– J. Doe
Jan 8 at 8:53
I am not even understanding if you have git IDs or not. If so, it should be easy which commit was a fork or a merge from which one(s). If not, see my comment above for other comments to do kind of text search inside git history.
– Patrick Mevzek
Jan 8 at 15:45
@PatrickMevzekI managed to get an overview from the history using following command: git rev-hist 123456..HEAD The correct ID came from the tag out of the other repository. I'll try your command later on. Thanks for you help.
– J. Doe
Jan 9 at 15:23
add a comment |
I'm currently manually building a Linux image with some specific drivers for a Xilinx Zynqmp device. Aside from the main Linux tree, there are 2 other mirrored Linux repositories, one from Xilinx and another where the driver was developed with.
I noticed some differences within the source files. I know about the "git blame" function and it tells me it is an older Xilinx developed file which was being used for the driver development.
My Question:
How do I track down the exact source file where the driver was build on? I would like to know which branch or tag was cloned/merged in order to build the driver. Because logically the driver developers kernel leaps behind the Xilinx dev kernel. How do I do this?
Any other git tips & tricks in this matter are very much welcome.
linux drivers git source trace
asked Jan 4 at 8:37
J. DoeJ. Doe
1
I'm currently manually building a Linux image with some specific drivers for a Xilinx Zynqmp device. Aside from the main Linux tree, there are 2 other mirrored Linux repositories, one from Xilinx and another where the driver was developed with.
I noticed some differences within the source files. I know about the "git blame" function and it tells me it is an older Xilinx developed file which was being used for the driver development.
My Question:
How do I track down the exact source file where the driver was build on? I would like to know which branch or tag was cloned/merged in order to build the driver. Because logically the driver developers kernel leaps behind the Xilinx dev kernel. How do I do this?
Any other git tips & tricks in this matter are very much welcome.
linux drivers git source trace
linux drivers git source trace
asked Jan 4 at 8:37
J. DoeJ. Doe
1
asked Jan 4 at 8:37
J. DoeJ. Doe
1
asked Jan 4 at 8:37
J. DoeJ. Doe
1
asked Jan 4 at 8:37
J. DoeJ. Doe
1
asked Jan 4 at 8:37
J. DoeJ. Doe
1
1
I am not sure to understand exactly your need, maybe you should add details on the specific git repository you are looking at, the files you are interested in, and what commands you tried already. As for tips and tricks, the following commands besidesgit blamecan be useful to do searches:git log -S,git log -Gandgit bisect.
– Patrick Mevzek
Jan 6 at 21:17
@PatrickMevzek I know the question is a bit vague. I have this driver from Analog Devices and they claim the Xilinx linux repo get's merged periodically with theirs. But it is very unclear to me which branch or tag was used as a base for their driver. I am looking for some tricks or tools to navigate through the giant Linux repository and track down what items the driver authors changed or not.
– J. Doe
Jan 8 at 8:53
I am not even understanding if you have git IDs or not. If so, it should be easy which commit was a fork or a merge from which one(s). If not, see my comment above for other comments to do kind of text search inside git history.
– Patrick Mevzek
Jan 8 at 15:45
@PatrickMevzekI managed to get an overview from the history using following command: git rev-hist 123456..HEAD The correct ID came from the tag out of the other repository. I'll try your command later on. Thanks for you help.
– J. Doe
Jan 9 at 15:23
add a comment |
I am not sure to understand exactly your need, maybe you should add details on the specific git repository you are looking at, the files you are interested in, and what commands you tried already. As for tips and tricks, the following commands besidesgit blamecan be useful to do searches:git log -S,git log -Gandgit bisect.
– Patrick Mevzek
Jan 6 at 21:17
@PatrickMevzek I know the question is a bit vague. I have this driver from Analog Devices and they claim the Xilinx linux repo get's merged periodically with theirs. But it is very unclear to me which branch or tag was used as a base for their driver. I am looking for some tricks or tools to navigate through the giant Linux repository and track down what items the driver authors changed or not.
– J. Doe
Jan 8 at 8:53
I am not even understanding if you have git IDs or not. If so, it should be easy which commit was a fork or a merge from which one(s). If not, see my comment above for other comments to do kind of text search inside git history.
– Patrick Mevzek
Jan 8 at 15:45
@PatrickMevzekI managed to get an overview from the history using following command: git rev-hist 123456..HEAD The correct ID came from the tag out of the other repository. I'll try your command later on. Thanks for you help.
– J. Doe
Jan 9 at 15:23
I am not sure to understand exactly your need, maybe you should add details on the specific git repository you are looking at, the files you are interested in, and what commands you tried already. As for tips and tricks, the following commands besides
git blame can be useful to do searches: git log -S, git log -G and git bisect.– Patrick Mevzek
Jan 6 at 21:17
I am not sure to understand exactly your need, maybe you should add details on the specific git repository you are looking at, the files you are interested in, and what commands you tried already. As for tips and tricks, the following commands besides
git blame can be useful to do searches: git log -S, git log -G and git bisect.– Patrick Mevzek
Jan 6 at 21:17
@PatrickMevzek I know the question is a bit vague. I have this driver from Analog Devices and they claim the Xilinx linux repo get's merged periodically with theirs. But it is very unclear to me which branch or tag was used as a base for their driver. I am looking for some tricks or tools to navigate through the giant Linux repository and track down what items the driver authors changed or not.
– J. Doe
Jan 8 at 8:53
@PatrickMevzek I know the question is a bit vague. I have this driver from Analog Devices and they claim the Xilinx linux repo get's merged periodically with theirs. But it is very unclear to me which branch or tag was used as a base for their driver. I am looking for some tricks or tools to navigate through the giant Linux repository and track down what items the driver authors changed or not.
– J. Doe
Jan 8 at 8:53
I am not even understanding if you have git IDs or not. If so, it should be easy which commit was a fork or a merge from which one(s). If not, see my comment above for other comments to do kind of text search inside git history.
– Patrick Mevzek
Jan 8 at 15:45
I am not even understanding if you have git IDs or not. If so, it should be easy which commit was a fork or a merge from which one(s). If not, see my comment above for other comments to do kind of text search inside git history.
– Patrick Mevzek
Jan 8 at 15:45
@PatrickMevzekI managed to get an overview from the history using following command: git rev-hist 123456..HEAD The correct ID came from the tag out of the other repository. I'll try your command later on. Thanks for you help.
– J. Doe
Jan 9 at 15:23
@PatrickMevzekI managed to get an overview from the history using following command: git rev-hist 123456..HEAD The correct ID came from the tag out of the other repository. I'll try your command later on. Thanks for you help.
– J. Doe
Jan 9 at 15:23
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492411%2fhow-to-trace-a-specific-historic-file-in-the-linux-kernel-tree-git-question%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492411%2fhow-to-trace-a-specific-historic-file-in-the-linux-kernel-tree-git-question%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I am not sure to understand exactly your need, maybe you should add details on the specific git repository you are looking at, the files you are interested in, and what commands you tried already. As for tips and tricks, the following commands besides
git blamecan be useful to do searches:git log -S,git log -Gandgit bisect.– Patrick Mevzek
Jan 6 at 21:17
@PatrickMevzek I know the question is a bit vague. I have this driver from Analog Devices and they claim the Xilinx linux repo get's merged periodically with theirs. But it is very unclear to me which branch or tag was used as a base for their driver. I am looking for some tricks or tools to navigate through the giant Linux repository and track down what items the driver authors changed or not.
– J. Doe
Jan 8 at 8:53
I am not even understanding if you have git IDs or not. If so, it should be easy which commit was a fork or a merge from which one(s). If not, see my comment above for other comments to do kind of text search inside git history.
– Patrick Mevzek
Jan 8 at 15:45
@PatrickMevzekI managed to get an overview from the history using following command: git rev-hist 123456..HEAD The correct ID came from the tag out of the other repository. I'll try your command later on. Thanks for you help.
– J. Doe
Jan 9 at 15:23