How to find out first author of a code in perforce
There is a c file in a source code repository(maintained by perforce) I am working on. Many people have made changes over time in that file. There is a while loop written inside that file. I want to know the author who has first introduced this while loop. If I use p4annotate then it is showing me some author who first removed this loop and later again added that loop. I mean he is not the first author of that while loop. Is there any way to know first author of that piece of code?
perforce
add a comment |
There is a c file in a source code repository(maintained by perforce) I am working on. Many people have made changes over time in that file. There is a while loop written inside that file. I want to know the author who has first introduced this while loop. If I use p4annotate then it is showing me some author who first removed this loop and later again added that loop. I mean he is not the first author of that while loop. Is there any way to know first author of that piece of code?
perforce
2
Use the-a
flag top4 annotate
– Bryan Pendleton
Nov 22 '18 at 17:20
add a comment |
There is a c file in a source code repository(maintained by perforce) I am working on. Many people have made changes over time in that file. There is a while loop written inside that file. I want to know the author who has first introduced this while loop. If I use p4annotate then it is showing me some author who first removed this loop and later again added that loop. I mean he is not the first author of that while loop. Is there any way to know first author of that piece of code?
perforce
There is a c file in a source code repository(maintained by perforce) I am working on. Many people have made changes over time in that file. There is a while loop written inside that file. I want to know the author who has first introduced this while loop. If I use p4annotate then it is showing me some author who first removed this loop and later again added that loop. I mean he is not the first author of that while loop. Is there any way to know first author of that piece of code?
perforce
perforce
asked Nov 22 '18 at 10:02
RanjuRanju
426
426
2
Use the-a
flag top4 annotate
– Bryan Pendleton
Nov 22 '18 at 17:20
add a comment |
2
Use the-a
flag top4 annotate
– Bryan Pendleton
Nov 22 '18 at 17:20
2
2
Use the
-a
flag to p4 annotate
– Bryan Pendleton
Nov 22 '18 at 17:20
Use the
-a
flag to p4 annotate
– Bryan Pendleton
Nov 22 '18 at 17:20
add a comment |
1 Answer
1
active
oldest
votes
Options to p4 annotate
that might be useful:
p4 annotate file#REV
starts the annotation at an earlier revision, so you could go back to the revision before the loop was deleted and see who'd last added it as of that revision.
p4 annotate -a file
shows all of the lines of the file, including those that have been deleted, so you'll see the original version of the while loop.
p4 annotate -I file
traces the origin of individual lines through merge operations from other files.
All of these options can be combined, so you can do things like p4 annotate -a -I file#START,#END
to get detailed information (including merge sources) about all the lines added to the file between two points in time.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fstackoverflow.com%2fquestions%2f53428367%2fhow-to-find-out-first-author-of-a-code-in-perforce%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Options to p4 annotate
that might be useful:
p4 annotate file#REV
starts the annotation at an earlier revision, so you could go back to the revision before the loop was deleted and see who'd last added it as of that revision.
p4 annotate -a file
shows all of the lines of the file, including those that have been deleted, so you'll see the original version of the while loop.
p4 annotate -I file
traces the origin of individual lines through merge operations from other files.
All of these options can be combined, so you can do things like p4 annotate -a -I file#START,#END
to get detailed information (including merge sources) about all the lines added to the file between two points in time.
add a comment |
Options to p4 annotate
that might be useful:
p4 annotate file#REV
starts the annotation at an earlier revision, so you could go back to the revision before the loop was deleted and see who'd last added it as of that revision.
p4 annotate -a file
shows all of the lines of the file, including those that have been deleted, so you'll see the original version of the while loop.
p4 annotate -I file
traces the origin of individual lines through merge operations from other files.
All of these options can be combined, so you can do things like p4 annotate -a -I file#START,#END
to get detailed information (including merge sources) about all the lines added to the file between two points in time.
add a comment |
Options to p4 annotate
that might be useful:
p4 annotate file#REV
starts the annotation at an earlier revision, so you could go back to the revision before the loop was deleted and see who'd last added it as of that revision.
p4 annotate -a file
shows all of the lines of the file, including those that have been deleted, so you'll see the original version of the while loop.
p4 annotate -I file
traces the origin of individual lines through merge operations from other files.
All of these options can be combined, so you can do things like p4 annotate -a -I file#START,#END
to get detailed information (including merge sources) about all the lines added to the file between two points in time.
Options to p4 annotate
that might be useful:
p4 annotate file#REV
starts the annotation at an earlier revision, so you could go back to the revision before the loop was deleted and see who'd last added it as of that revision.
p4 annotate -a file
shows all of the lines of the file, including those that have been deleted, so you'll see the original version of the while loop.
p4 annotate -I file
traces the origin of individual lines through merge operations from other files.
All of these options can be combined, so you can do things like p4 annotate -a -I file#START,#END
to get detailed information (including merge sources) about all the lines added to the file between two points in time.
answered Nov 22 '18 at 17:29
Sam StaffordSam Stafford
12.2k819
12.2k819
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53428367%2fhow-to-find-out-first-author-of-a-code-in-perforce%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
2
Use the
-a
flag top4 annotate
– Bryan Pendleton
Nov 22 '18 at 17:20