Re: does a stash *need* any reference to the branch on which it was created?

2018-06-04 Thread Robert P. J. Day
On Mon, 4 Jun 2018, Junio C Hamano wrote: > "Robert P. J. Day" writes: > > > i realize that, when you "git stash push", stash graciously > > saves the branch you were on as part of the commit message, but > > does any subsequent stash operation technically *need* that branch > > name? > > It

Re: does a stash *need* any reference to the branch on which it was created?

2018-06-03 Thread Junio C Hamano
"Robert P. J. Day" writes: > i realize that, when you "git stash push", stash graciously saves > the branch you were on as part of the commit message, but does any > subsequent stash operation technically *need* that branch name? It is not "saves", but "the message it automatically generates

Re: does a stash *need* any reference to the branch on which it was created?

2018-06-02 Thread Thomas Gummerer
On 06/02, Robert P. J. Day wrote: > > i realize that, when you "git stash push", stash graciously saves > the branch you were on as part of the commit message, but does any > subsequent stash operation technically *need* that branch name? $ git stash list stash@{0}: WIP on master:

does a stash *need* any reference to the branch on which it was created?

2018-06-02 Thread Robert P. J. Day
i realize that, when you "git stash push", stash graciously saves the branch you were on as part of the commit message, but does any subsequent stash operation technically *need* that branch name? it doesn't seem like it -- even "git stash branch" really only needs the commit that was the