git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2014, #01; Fri, 1)
Date: Wed, 6 Aug 2014 04:11:02 -0400	[thread overview]
Message-ID: <20140806081102.GA1646@peff.net> (raw)
In-Reply-To: <xmqqy4v7uax0.fsf@gitster.dls.corp.google.com>

On Fri, Aug 01, 2014 at 03:01:31PM -0700, Junio C Hamano wrote:

> * jk/stash-list-p (2014-07-30) 7 commits
>  - SQUASH??? future-proof, log --cc should imply -p without being told
>  - stash: show combined diff with "stash show"
>  - stash: default listing to "--cc --simplify-combined-diff"
>  - add --simplify-combined-diff option
>  - pretty: make empty userformats truly empty
>  - pretty: treat "--format=" as an empty userformat
>  - revision: drop useless string offset when parsing "--pretty"
> 
>  Teach "git stash list -p" to DWIM to "git stash list -p --cc", with
>  even nicer twist to collapse combined diff from identical two
>  parents into a regular diff.

What do you want to do with this topic?

I think we want to drop the "stash show" patch, based on the discussion
we had.  The first three patches are nominally prep for that final
patch, but actually are things I've often wanted over the years. I'd be
glad if they made it in separately, but there were some compatibility
questions.

As clever as I find the --simplify-combined-diff patch, I think we came
to the conclusion that "--first-parent" is probably the reasonable
choice. It matches "stash show", and it's simple and obvious. Do we just
want a patch to specify "--first-parent" to stash-log? That would make
"-p" just work. The only downside is that there isn't a good way to turn
it off. Is it enough to say "if you want to do something clever, use
git-log"?

Or do we want to scrap the whole thing and try to update the
documentation to make it more clear why "-p" by itself doesn't do
anything?

-Peff

  reply	other threads:[~2014-08-06  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01 22:01 What's cooking in git.git (Aug 2014, #01; Fri, 1) Junio C Hamano
2014-08-06  8:11 ` Jeff King [this message]
2014-08-06 17:12   ` Junio C Hamano
2014-08-06 18:35     ` [PATCH] stash: default listing to working-tree diff Jeff King
2014-08-07 21:39       ` Junio C Hamano

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=20140806081102.GA1646@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).