Is it possible to create a branch from a stash using the stash name?
0
I know
git stash branch branchname
creates a new branch using the most recent stash
and
git stash branch branchname stash@{index}
creates a new branch using a stash at a given index. But, is it possible to do something like this?
git stash branch branchname stashname
Note: This didn't work
git stash branch branchname stash^{/name}
git git-branch git-stash
edited Nov 19 '18 at 17:04
Micha Wiedenmann
10.3k1364104
asked Nov 19 '18 at 17:00
AdriangAdriang
918
|
show 2 more comments
0
I know
git stash branch branchname
creates a new branch using the most recent stash
and
git stash branch branchname stash@{index}
creates a new branch using a stash at a given index. But, is it possible to do something like this?
git stash branch branchname stashname
Note: This didn't work
git stash branch branchname stash^{/name}
git git-branch git-stash
edited Nov 19 '18 at 17:04
Micha Wiedenmann
10.3k1364104
asked Nov 19 '18 at 17:00
AdriangAdriang
918
What do you mean by "stashname"? The stash names arestash@{<number>}.
– torek
Nov 19 '18 at 17:21
@torek A stash can be saved with a name, or more accurately, a message "git stash save "guacamole sauce WIP" and then applied using that message "git stash apply stash^{/guacamo}" as discussed here stackoverflow.com/questions/11269256/….
– Adriang
Nov 19 '18 at 17:31
Ah. That's technically a message, not a name. It just goes into the commit message for the work-tree. Unfortunately, the answer to which you linked is also completely wrong. (See this other answer to that same question, which appears to be correct.)
– torek
Nov 19 '18 at 17:39
That's why I included, "or more accurately, a message" comment :) In common usage, I'd heard stashes with messages referred to as "named stashes", with the understanding that under the covers, they are stashes with an associated message. Good point about that incorrect answer. So, if we can apply a stash by using the index position can we also do so by message?
– Adriang
Nov 19 '18 at 18:21
1
You can certainly do a search (usinggit log -g --grep) and use that to get the stash index or hash ID. You'll need the index, with thestash@{number}spelling, for operations that want to also drop the stash: the hash ID alone won't suffice here. Sincegit stash branchdrops the stash, it needs the index. Very recent Git versions accept a raw number, e.g.,2meansstash@{2}, but for older Git compatibility, you might want to stick with thestash@{...}syntax for some time.
– torek
Nov 19 '18 at 18:47
|
show 2 more comments
0
0
0
I know
git stash branch branchname
creates a new branch using the most recent stash
and
git stash branch branchname stash@{index}
creates a new branch using a stash at a given index. But, is it possible to do something like this?
git stash branch branchname stashname
Note: This didn't work
git stash branch branchname stash^{/name}
git git-branch git-stash
edited Nov 19 '18 at 17:04
Micha Wiedenmann
10.3k1364104
asked Nov 19 '18 at 17:00
AdriangAdriang
918
I know
git stash branch branchname
creates a new branch using the most recent stash
and
git stash branch branchname stash@{index}
creates a new branch using a stash at a given index. But, is it possible to do something like this?
git stash branch branchname stashname
Note: This didn't work
git stash branch branchname stash^{/name}
git git-branch git-stash
git git-branch git-stash
edited Nov 19 '18 at 17:04
Micha Wiedenmann
10.3k1364104
asked Nov 19 '18 at 17:00
AdriangAdriang
918
edited Nov 19 '18 at 17:04
Micha Wiedenmann
10.3k1364104
asked Nov 19 '18 at 17:00
AdriangAdriang
918
edited Nov 19 '18 at 17:04
Micha Wiedenmann
10.3k1364104
edited Nov 19 '18 at 17:04
Micha Wiedenmann
10.3k1364104
edited Nov 19 '18 at 17:04
Micha Wiedenmann
10.3k1364104
10.3k1364104
asked Nov 19 '18 at 17:00
AdriangAdriang
918
asked Nov 19 '18 at 17:00
AdriangAdriang
918
asked Nov 19 '18 at 17:00
AdriangAdriang
918
918
What do you mean by "stashname"? The stash names arestash@{<number>}.
– torek
Nov 19 '18 at 17:21
@torek A stash can be saved with a name, or more accurately, a message "git stash save "guacamole sauce WIP" and then applied using that message "git stash apply stash^{/guacamo}" as discussed here stackoverflow.com/questions/11269256/….
– Adriang
Nov 19 '18 at 17:31
Ah. That's technically a message, not a name. It just goes into the commit message for the work-tree. Unfortunately, the answer to which you linked is also completely wrong. (See this other answer to that same question, which appears to be correct.)
– torek
Nov 19 '18 at 17:39
That's why I included, "or more accurately, a message" comment :) In common usage, I'd heard stashes with messages referred to as "named stashes", with the understanding that under the covers, they are stashes with an associated message. Good point about that incorrect answer. So, if we can apply a stash by using the index position can we also do so by message?
– Adriang
Nov 19 '18 at 18:21
1
You can certainly do a search (usinggit log -g --grep) and use that to get the stash index or hash ID. You'll need the index, with thestash@{number}spelling, for operations that want to also drop the stash: the hash ID alone won't suffice here. Sincegit stash branchdrops the stash, it needs the index. Very recent Git versions accept a raw number, e.g.,2meansstash@{2}, but for older Git compatibility, you might want to stick with thestash@{...}syntax for some time.
– torek
Nov 19 '18 at 18:47
|
show 2 more comments
What do you mean by "stashname"? The stash names arestash@{<number>}.
– torek
Nov 19 '18 at 17:21
@torek A stash can be saved with a name, or more accurately, a message "git stash save "guacamole sauce WIP" and then applied using that message "git stash apply stash^{/guacamo}" as discussed here stackoverflow.com/questions/11269256/….
– Adriang
Nov 19 '18 at 17:31
Ah. That's technically a message, not a name. It just goes into the commit message for the work-tree. Unfortunately, the answer to which you linked is also completely wrong. (See this other answer to that same question, which appears to be correct.)
– torek
Nov 19 '18 at 17:39
That's why I included, "or more accurately, a message" comment :) In common usage, I'd heard stashes with messages referred to as "named stashes", with the understanding that under the covers, they are stashes with an associated message. Good point about that incorrect answer. So, if we can apply a stash by using the index position can we also do so by message?
– Adriang
Nov 19 '18 at 18:21
1
You can certainly do a search (usinggit log -g --grep) and use that to get the stash index or hash ID. You'll need the index, with thestash@{number}spelling, for operations that want to also drop the stash: the hash ID alone won't suffice here. Sincegit stash branchdrops the stash, it needs the index. Very recent Git versions accept a raw number, e.g.,2meansstash@{2}, but for older Git compatibility, you might want to stick with thestash@{...}syntax for some time.
– torek
Nov 19 '18 at 18:47
What do you mean by "stashname"? The stash names are
stash@{<number>}.– torek
Nov 19 '18 at 17:21
What do you mean by "stashname"? The stash names are
stash@{<number>}.– torek
Nov 19 '18 at 17:21
@torek A stash can be saved with a name, or more accurately, a message "git stash save "guacamole sauce WIP" and then applied using that message "git stash apply stash^{/guacamo}" as discussed here stackoverflow.com/questions/11269256/….
– Adriang
Nov 19 '18 at 17:31
@torek A stash can be saved with a name, or more accurately, a message "git stash save "guacamole sauce WIP" and then applied using that message "git stash apply stash^{/guacamo}" as discussed here stackoverflow.com/questions/11269256/….
– Adriang
Nov 19 '18 at 17:31
Ah. That's technically a message, not a name. It just goes into the commit message for the work-tree. Unfortunately, the answer to which you linked is also completely wrong. (See this other answer to that same question, which appears to be correct.)
– torek
Nov 19 '18 at 17:39
Ah. That's technically a message, not a name. It just goes into the commit message for the work-tree. Unfortunately, the answer to which you linked is also completely wrong. (See this other answer to that same question, which appears to be correct.)
– torek
Nov 19 '18 at 17:39
That's why I included, "or more accurately, a message" comment :) In common usage, I'd heard stashes with messages referred to as "named stashes", with the understanding that under the covers, they are stashes with an associated message. Good point about that incorrect answer. So, if we can apply a stash by using the index position can we also do so by message?
– Adriang
Nov 19 '18 at 18:21
That's why I included, "or more accurately, a message" comment :) In common usage, I'd heard stashes with messages referred to as "named stashes", with the understanding that under the covers, they are stashes with an associated message. Good point about that incorrect answer. So, if we can apply a stash by using the index position can we also do so by message?
– Adriang
Nov 19 '18 at 18:21
1
1
You can certainly do a search (using
git log -g --grep) and use that to get the stash index or hash ID. You'll need the index, with the stash@{number} spelling, for operations that want to also drop the stash: the hash ID alone won't suffice here. Since git stash branch drops the stash, it needs the index. Very recent Git versions accept a raw number, e.g., 2 means stash@{2}, but for older Git compatibility, you might want to stick with the stash@{...} syntax for some time.– torek
Nov 19 '18 at 18:47
You can certainly do a search (using
git log -g --grep) and use that to get the stash index or hash ID. You'll need the index, with the stash@{number} spelling, for operations that want to also drop the stash: the hash ID alone won't suffice here. Since git stash branch drops the stash, it needs the index. Very recent Git versions accept a raw number, e.g., 2 means stash@{2}, but for older Git compatibility, you might want to stick with the stash@{...} syntax for some time.– torek
Nov 19 '18 at 18:47
|
show 2 more comments
0
active
oldest
votes
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
});
}
});
draft saved
draft discarded
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%2f53379417%2fis-it-possible-to-create-a-branch-from-a-stash-using-the-stash-name%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
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f53379417%2fis-it-possible-to-create-a-branch-from-a-stash-using-the-stash-name%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
What do you mean by "stashname"? The stash names are
stash@{<number>}.– torek
Nov 19 '18 at 17:21
@torek A stash can be saved with a name, or more accurately, a message "git stash save "guacamole sauce WIP" and then applied using that message "git stash apply stash^{/guacamo}" as discussed here stackoverflow.com/questions/11269256/….
– Adriang
Nov 19 '18 at 17:31
Ah. That's technically a message, not a name. It just goes into the commit message for the work-tree. Unfortunately, the answer to which you linked is also completely wrong. (See this other answer to that same question, which appears to be correct.)
– torek
Nov 19 '18 at 17:39
That's why I included, "or more accurately, a message" comment :) In common usage, I'd heard stashes with messages referred to as "named stashes", with the understanding that under the covers, they are stashes with an associated message. Good point about that incorrect answer. So, if we can apply a stash by using the index position can we also do so by message?
– Adriang
Nov 19 '18 at 18:21
1
You can certainly do a search (using
git log -g --grep) and use that to get the stash index or hash ID. You'll need the index, with thestash@{number}spelling, for operations that want to also drop the stash: the hash ID alone won't suffice here. Sincegit stash branchdrops the stash, it needs the index. Very recent Git versions accept a raw number, e.g.,2meansstash@{2}, but for older Git compatibility, you might want to stick with thestash@{...}syntax for some time.– torek
Nov 19 '18 at 18:47