From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Fabio Augusto Dal Castel <fdcastel@gmail.com>,
Brandon Casey <casey@nrlssc.navy.mil>,
git@vger.kernel.org
Subject: Re: [RFC] New command: 'git snapshot'.
Date: Tue, 10 Feb 2009 18:38:02 -0500 [thread overview]
Message-ID: <20090210233801.GA9617@coredump.intra.peff.net> (raw)
In-Reply-To: <7vy6wdkhzk.fsf@gitster.siamese.dyndns.org>
On Tue, Feb 10, 2009 at 03:08:31PM -0800, Junio C Hamano wrote:
> >> Remember that 'stash' is actually TWO commands in one:
> >> * Save current state
> >> * Reset to HEAD
> >>
> >> My primary reason to use snapshots is to AVOID the second step.
> >
> > Doesn't that argue for "git stash --no-reset" or similar instead of a
> > separate command?
>
> How is it different from "git stash create"?
According to the man page, "git stash create" doesn't even store it in a
ref. I think the point would be to store it in a ref somewhere (as "git
stash save" does), but not do the reset.
But I have never once used "git stash create", so maybe I am
misunderstanding it.
-Peff
next prev parent reply other threads:[~2009-02-10 23:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 18:54 [RFC] New command: 'git snapshot' Fabio Augusto Dal Castel
2009-02-09 19:52 ` Giuseppe Bilotta
[not found] ` <38cfbb550902101232l4c83b6dfjc70e1e2f79a8c3c1@mail.gmail.com>
2009-02-10 20:48 ` Fabio Augusto Dal Castel
2009-02-09 22:36 ` Brandon Casey
2009-02-10 4:51 ` Sitaram Chamarty
2009-02-10 19:47 ` Jon Loeliger
2009-02-10 20:31 ` Junio C Hamano
2009-02-11 1:22 ` Sitaram Chamarty
2009-02-10 20:40 ` Fabio Augusto Dal Castel
2009-02-10 23:00 ` Jeff King
2009-02-10 23:08 ` Junio C Hamano
2009-02-10 23:38 ` Jeff King [this message]
2009-02-10 23:39 ` Geoffrey Lee
2009-02-11 13:43 ` Jeff King
2009-02-11 9:04 ` Matthieu Moy
2009-02-11 20:40 ` Fabio Augusto Dal Castel
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 23:58 Ulrik Sverdrup
2009-02-11 0:05 ` Ulrik Sverdrup
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=20090210233801.GA9617@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=casey@nrlssc.navy.mil \
--cc=fdcastel@gmail.com \
--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).