On Jan 23, 2013, at 7:39 AM, Geert Janssens <janssens-ge...@telenet.be> wrote:
> On 23-01-13 16:16, Derek Atkins wrote: >> John Ralls <jra...@ceridwen.us> writes: >> >>> On Jan 23, 2013, at 3:47 AM, Geert Janssens <janssens-ge...@telenet.be> >>> wrote: >>> >>>> I have verified the procedure to work. Thanks. I did some very minor >>>> modifications, which I hope clear up some small confusions. >>>> >>>> Any suggestion to migrate the stashed stack ? >>>> >>> Sorry, what do you mean by "stashed stack"? >> I suspect he means "git stash"? >> >>> Regards, >>> John Ralls >> -derek >> > Indeed, I have some unfinished small experiments that are not committed, but > instead set aside using git stash because something else interrupted me > before these experiments were good enough to commit. > > With git stash save, you can quickly push your current index and working copy > in some kind of stack of "interrupted" work. It can later be recovered with > git stash pop <stash number>. > > If nothing else, I can try to > - save them in commits > - cherry-pick those > - then kind of "uncommit" with perhaps revert or soft reset > - and stash again Oh, OK. I don't keep a lot of stashes around. But I found some suggestions: http://stackoverflow.com/questions/2160638/how-can-i-format-patch-with-what-i-stash-away and http://superuser.com/questions/409228/how-can-i-share-a-git-stash looks particularly intriguing; the implication is that you can do it in a single shot. What he doesn't say is that you'll need to use git update-references to recalibrate the stash in "gnucash-new" to point to "otherstash". Regards, John Ralls _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
