git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@fluxnic.net>
To: skillzero@gmail.com
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Global reflog?
Date: Sun, 14 Feb 2010 23:24:49 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1002142320440.1946@xanadu.home> (raw)
In-Reply-To: <2729632a1002141414l4c4ccd82j32693e6e3bd02bc5@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1261 bytes --]

On Sun, 14 Feb 2010, skillzero@gmail.com wrote:

> On Sun, Feb 14, 2010 at 1:56 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
> > On Sun, 14 Feb 2010, skillzero@gmail.com wrote:
> >
> >> Is there a way to have git maintain a single reflog across all
> >> branches (and stashes)? I switch between branches, create and delete
> >> branches, stash save and pop, etc. frequently and it would be great
> >> for me if there was a way to have a global reflog that showed every
> >> operation, independent of a particular branch. Is there some way to
> >> enable this?
> >
> > You have it already.  It is the "HEAD" reflog.
> 
> I don't seem to see any stash activity. For example, I made a test
> change, did git stash, and then git stash pop. When I do git reflog, I
> don't see the stash commit or the delete of the stash. Is there a way
> to enable that?

It is true that stash doesn't touch HEAD.  So logically the stash 
operations should not end up in the HEAD reflog.  But maybe creating a 
reflog only for stashed states could be a good thing.

I personally don't use stash that much since I've grown the habit of 
saving temporary states to a temporary branch before git-stash even 
existed, which in that case is always captured by the HEAD reflog.


Nicolas

      reply	other threads:[~2010-02-15  4:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 21:49 Global reflog? skillzero
2010-02-14 21:56 ` Nicolas Pitre
2010-02-14 22:14   ` skillzero
2010-02-15  4:24     ` Nicolas Pitre [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=alpine.LFD.2.00.1002142320440.1946@xanadu.home \
    --to=nico@fluxnic.net \
    --cc=git@vger.kernel.org \
    --cc=skillzero@gmail.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).