From: "Stefan Näwe" <stefan.naewe@atlas-elektronik.com>
To: David Aguilar <davvid@gmail.com>
Cc: dexen deVries <dexen.devries@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Feature requset: listing of current stash in git gui
Date: Tue, 22 Nov 2011 16:19:14 +0100 [thread overview]
Message-ID: <4ECBBD72.40101@atlas-elektronik.com> (raw)
In-Reply-To: <-8099236111493298698@unknownmsgid>
Am 22.11.2011 11:24, schrieb David Aguilar:
> On Nov 21, 2011, at 4:41 AM, dexen deVries <dexen.devries@gmail.com> wrote:
>
>> On Monday 21 of November 2011 11:53:03 Stefan Näwe wrote:
>>> You can simply put the following in your ~/.gitconfig:
>>>
>>> [guitool "Stash/show"]
>>> cmd = git stash show -p
>>> [guitool "Stash/list"]
>>> cmd = git stash list
>>> [guitool "Stash/pop"]
>>> cmd = git stash pop
>>> [guitool "Stash/drop"]
>>> cmd = git stash drop
>>> confirm = yes
>>
>> that's nice, but doesn't list visually the stashed changes. I'd rather have a
>> listing similar to Unstanged Changes / Staged Changes, with ability to view
>> line-by-line diff just like for Changes.
>
> [blatant plug]
>
> git-cola has this feature.
>>
>
> http://git-cola.github.com/
Yeah, right. I totally forgot about git cola.
But I guess there's no way of starting only the stash view like the 'DAG'
view, is there ?
Stefan
--
----------------------------------------------------------------
/dev/random says: This is a Tagline mirror><rorrim enilgaT a si sihT
python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')"
next prev parent reply other threads:[~2011-11-22 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 10:00 Feature requset: listing of current stash in git gui dexen deVries
2011-11-21 10:53 ` Stefan Näwe
2011-11-21 12:41 ` dexen deVries
[not found] ` <30417194.1411.1321907485839.JavaMail.mobile-sync@ieja14>
2011-11-22 10:24 ` David Aguilar
2011-11-22 15:19 ` Stefan Näwe [this message]
2011-11-23 11:20 ` David Aguilar
2011-11-23 11:24 ` Stefan Näwe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ECBBD72.40101@atlas-elektronik.com \
--to=stefan.naewe@atlas-elektronik.com \
--cc=davvid@gmail.com \
--cc=dexen.devries@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.