What's the difference between q and d in git add --patch?
I was trying out git add --patch
and typing ? at this prompt:
Stage this hunk [y,n,q,a,d,e,?]
gives me the explanation of the commands, but I can't understand the difference between these:
q - quit; do not stage this hunk or any of the remaining ones
d - do not stage this hunk or any of the later hunks in the file
(using Git version 2.20.1)
git
add a comment |
I was trying out git add --patch
and typing ? at this prompt:
Stage this hunk [y,n,q,a,d,e,?]
gives me the explanation of the commands, but I can't understand the difference between these:
q - quit; do not stage this hunk or any of the remaining ones
d - do not stage this hunk or any of the later hunks in the file
(using Git version 2.20.1)
git
1
Did you see this comment "q does not reset any previously staged changes. Whatever you have already staged remains staged" in this question stackoverflow.com/questions/10605405/…
– lx07
Jan 24 at 18:31
@lx07 Thanks! No I hadn't seen it. But from what I've seend
does not reset previously staged changes either..?
– Echo
Jan 24 at 19:45
1
I don't know - "d will proceed to the next file" apparently. I don't know the answer - just thought the comments on that question were relevant to your question and may make sense to you. Hopefully someone better informed can add more...
– lx07
Jan 24 at 20:31
oh, this makes sense, thanks!
– Echo
Jan 25 at 14:37
add a comment |
I was trying out git add --patch
and typing ? at this prompt:
Stage this hunk [y,n,q,a,d,e,?]
gives me the explanation of the commands, but I can't understand the difference between these:
q - quit; do not stage this hunk or any of the remaining ones
d - do not stage this hunk or any of the later hunks in the file
(using Git version 2.20.1)
git
I was trying out git add --patch
and typing ? at this prompt:
Stage this hunk [y,n,q,a,d,e,?]
gives me the explanation of the commands, but I can't understand the difference between these:
q - quit; do not stage this hunk or any of the remaining ones
d - do not stage this hunk or any of the later hunks in the file
(using Git version 2.20.1)
git
git
edited Jan 24 at 17:22
Echo
asked Jan 24 at 17:16
EchoEcho
6818
6818
1
Did you see this comment "q does not reset any previously staged changes. Whatever you have already staged remains staged" in this question stackoverflow.com/questions/10605405/…
– lx07
Jan 24 at 18:31
@lx07 Thanks! No I hadn't seen it. But from what I've seend
does not reset previously staged changes either..?
– Echo
Jan 24 at 19:45
1
I don't know - "d will proceed to the next file" apparently. I don't know the answer - just thought the comments on that question were relevant to your question and may make sense to you. Hopefully someone better informed can add more...
– lx07
Jan 24 at 20:31
oh, this makes sense, thanks!
– Echo
Jan 25 at 14:37
add a comment |
1
Did you see this comment "q does not reset any previously staged changes. Whatever you have already staged remains staged" in this question stackoverflow.com/questions/10605405/…
– lx07
Jan 24 at 18:31
@lx07 Thanks! No I hadn't seen it. But from what I've seend
does not reset previously staged changes either..?
– Echo
Jan 24 at 19:45
1
I don't know - "d will proceed to the next file" apparently. I don't know the answer - just thought the comments on that question were relevant to your question and may make sense to you. Hopefully someone better informed can add more...
– lx07
Jan 24 at 20:31
oh, this makes sense, thanks!
– Echo
Jan 25 at 14:37
1
1
Did you see this comment "q does not reset any previously staged changes. Whatever you have already staged remains staged" in this question stackoverflow.com/questions/10605405/…
– lx07
Jan 24 at 18:31
Did you see this comment "q does not reset any previously staged changes. Whatever you have already staged remains staged" in this question stackoverflow.com/questions/10605405/…
– lx07
Jan 24 at 18:31
@lx07 Thanks! No I hadn't seen it. But from what I've seen
d
does not reset previously staged changes either..?– Echo
Jan 24 at 19:45
@lx07 Thanks! No I hadn't seen it. But from what I've seen
d
does not reset previously staged changes either..?– Echo
Jan 24 at 19:45
1
1
I don't know - "d will proceed to the next file" apparently. I don't know the answer - just thought the comments on that question were relevant to your question and may make sense to you. Hopefully someone better informed can add more...
– lx07
Jan 24 at 20:31
I don't know - "d will proceed to the next file" apparently. I don't know the answer - just thought the comments on that question were relevant to your question and may make sense to you. Hopefully someone better informed can add more...
– lx07
Jan 24 at 20:31
oh, this makes sense, thanks!
– Echo
Jan 25 at 14:37
oh, this makes sense, thanks!
– Echo
Jan 25 at 14:37
add a comment |
1 Answer
1
active
oldest
votes
As @lx07 mentioned in his comment, d
will proceed to the next file while q
will quit the whole process.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1398015%2fwhats-the-difference-between-q-and-d-in-git-add-patch%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
As @lx07 mentioned in his comment, d
will proceed to the next file while q
will quit the whole process.
add a comment |
As @lx07 mentioned in his comment, d
will proceed to the next file while q
will quit the whole process.
add a comment |
As @lx07 mentioned in his comment, d
will proceed to the next file while q
will quit the whole process.
As @lx07 mentioned in his comment, d
will proceed to the next file while q
will quit the whole process.
answered Jan 25 at 14:38
EchoEcho
6818
6818
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1398015%2fwhats-the-difference-between-q-and-d-in-git-add-patch%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
1
Did you see this comment "q does not reset any previously staged changes. Whatever you have already staged remains staged" in this question stackoverflow.com/questions/10605405/…
– lx07
Jan 24 at 18:31
@lx07 Thanks! No I hadn't seen it. But from what I've seen
d
does not reset previously staged changes either..?– Echo
Jan 24 at 19:45
1
I don't know - "d will proceed to the next file" apparently. I don't know the answer - just thought the comments on that question were relevant to your question and may make sense to you. Hopefully someone better informed can add more...
– lx07
Jan 24 at 20:31
oh, this makes sense, thanks!
– Echo
Jan 25 at 14:37