From: "Øystein Walle" <oystwa@gmail.com>
To: git@vger.kernel.org
Subject: Re: stash-p broken?
Date: Tue, 29 Jul 2014 06:45:24 +0000 (UTC) [thread overview]
Message-ID: <loom.20140729T084120-450@post.gmane.org> (raw)
In-Reply-To: 20140729025940.GA8640@vauxhall.crustytoothpaste.net
brian m. carlson <sandals <at> crustytoothpaste.net> writes:
>
> On Mon, Jul 28, 2014 at 05:56:28PM -0700, Michael Migdol wrote:
> > Sorry for error -- I meant: git stash list -p, not git stash -p.
> >
> > On Mon, Jul 28, 2014 at 5:38 PM, Michael Migdol <michael-spam <at>
migdol.net> wrote:
> > > I recently upgraded from Ubuntu 13.10 to Ubuntu 14.04. After doing so,
> > > "git stash -p" stopped working. (It apparently is ignoring the -p
> > > parameter). I'm not sure what version I was using previously, but after
> > > some experimentation, I see that:
> > >
> > > version 1.7.12.2 : stash -p DOES work
> > > version 1.9.3 : doesn't work
> > > version 2.0.3 : doesn't work
>
> Under the hood, we do:
>
> git log --format="%gd: %gs" -g "$ <at> " refs/stash --
>
> But it looks like git log ignores -p if -g is provided.
>
Unfortunately I don't have much to add...
I have a weird issue where `git stash list -p` does not show a diff, but
`~/usr/bin/git stash list -p` does, for the exact same version of Git.
However, the underlying command does not show a diff in either case,
even though I can tell that is the one being executed (with set -x
inserted into .../libexec/git-stash).
This is so weird that I think it's my system's fault. I have to do some
more digging.
Øsse
next prev parent reply other threads:[~2014-07-29 6:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 0:38 stash-p broken? Michael Migdol
2014-07-29 0:56 ` Michael Migdol
2014-07-29 2:59 ` brian m. carlson
2014-07-29 6:45 ` Øystein Walle [this message]
2014-07-29 9:23 ` Jeff King
2014-07-29 17:00 ` Junio C Hamano
2014-07-29 17:43 ` Jeff King
2014-07-29 18:23 ` Junio C Hamano
2014-07-31 0:23 ` Jeff King
2014-07-31 16:49 ` Junio C Hamano
2014-07-29 19:27 ` Junio C Hamano
2014-07-31 0:16 ` Jeff King
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=loom.20140729T084120-450@post.gmane.org \
--to=oystwa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).