git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Konstantin Khomoutov <kostix+git@007spb.ru>
Cc: Fabrizio Mancin <fabman08@gmail.com>, git@vger.kernel.org
Subject: Re: Stash Feature
Date: Wed, 03 Jun 2015 11:53:21 -0700	[thread overview]
Message-ID: <86lhg0vd26.fsf@red.stonehenge.com> (raw)
In-Reply-To: <20150603185358.a30d606cc0c475cb17a048c7@domain007.com> (Konstantin Khomoutov's message of "Wed, 3 Jun 2015 18:53:58 +0300")

>>>>> "Konstantin" == Konstantin Khomoutov <kostix+git@007spb.ru> writes:

Konstantin> On Wed, 3 Jun 2015 17:22:57 +0200
Konstantin> Fabrizio Mancin <fabman08@gmail.com> wrote:

>> I've a little request for you.
>> What about saving date-time on git stash save command and show it on
>> git stash show stash@{xxx}?
>> I think it is a useful poperty to save.
>> 
>> What do you think about it?

Konstantin> This information is already there as a stash entry is
Konstantin> internally represented as a commit (with one or more
Konstantin> parents), and being a commit, it possess all the standard
Konstantin> attributes of a commit, including the creation timestamp.

git stash list can take a --format as well.  Here's a couple of my
aliases:

  sl = stash list --pretty='%gd: %h [%ar] %s'
  stashed = stash list --pretty='%gd: %Cred%h%Creset %Cgreen[%ar]%Creset %s'


-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix consulting, Technical writing, Comedy, etc. etc.
Still trying to think of something clever for the fourth line of this .sig

      reply	other threads:[~2015-06-03 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 15:22 Stash Feature Fabrizio Mancin
2015-06-03 15:53 ` Konstantin Khomoutov
2015-06-03 18:53   ` Randal L. Schwartz [this message]

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=86lhg0vd26.fsf@red.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=fabman08@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kostix+git@007spb.ru \
    /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).