From: Miles Bader <miles@gnu.org>
To: Stephan Beyer <s-beyer@gmx.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Anders Melchiorsen <mail@cup.kalibalik.dk>,
Brandon Casey <casey@nrlssc.navy.mil>,
David Kastrup <dak@gnu.org>,
git@vger.kernel.org
Subject: Re: Usability of git stash
Date: Mon, 20 Oct 2008 18:36:05 +0900 [thread overview]
Message-ID: <buor66bd2wq.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <20081019231239.GA23692@leksak.fem-net> (Stephan Beyer's message of "Mon, 20 Oct 2008 01:12:39 +0200")
Stephan Beyer <s-beyer@gmx.net> writes:
> I, for example, have a stash in which some "valgrind ..." string is
> prepended to some lines in some test scripts. I apply the stash on
> different branches and after testing I reset the file (or checkout -f
> another branch). I never really want to commit these changes.
I'd just use an appropriate patch file kept around in a parent dir or
something... :-)
-Miles
--
People who are more than casually interested in computers should have at
least some idea of what the underlying hardware is like. Otherwise the
programs they write will be pretty weird. -- Donald Knuth
next prev parent reply other threads:[~2008-10-20 9:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 19:24 Usability of git stash Anders Melchiorsen
2008-10-15 19:31 ` Brandon Casey
2008-10-16 11:24 ` David Kastrup
2008-10-16 15:22 ` Brandon Casey
2008-10-18 9:26 ` Anders Melchiorsen
2008-10-19 18:40 ` Shawn O. Pearce
2008-10-19 21:08 ` Leo Razoumov
2008-10-19 21:49 ` Shawn O. Pearce
2008-10-19 23:12 ` Stephan Beyer
2008-10-20 9:36 ` Miles Bader [this message]
2008-10-20 0:36 ` Jeff King
2008-10-20 5:29 ` Junio C Hamano
2008-10-20 5:23 ` Miles Bader
2008-10-20 9:49 ` Andreas Ericsson
2008-10-20 16:33 ` Brandon Casey
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=buor66bd2wq.fsf@dhapc248.dev.necel.com \
--to=miles@gnu.org \
--cc=casey@nrlssc.navy.mil \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=mail@cup.kalibalik.dk \
--cc=s-beyer@gmx.net \
--cc=spearce@spearce.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).