From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Benoit SIGOURE <tsuna@lrde.epita.fr>
Cc: Neil Macneale <mac4-git@theory.org>, git <git@vger.kernel.org>
Subject: Re: Stashing untracked files
Date: Sat, 29 Sep 2007 22:51:32 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709292248400.28395@racer.site> (raw)
In-Reply-To: <EEE8F630-AE62-4425-96A0-239D54724DF4@lrde.epita.fr>
Hi,
On Sat, 29 Sep 2007, Benoit SIGOURE wrote:
> On Sep 29, 2007, at 11:03 PM, Johannes Schindelin wrote:
>
> > Instead this is what you _should_ do:
> >
> > git add <the files that you care about>
> > git stash
>
> You could stash untracked files that are not ignored (I personally
> ignore *.o, *.a and the like).
And what if you happen to forget to ignore that? Or if you happen to
have an strace log in some file (which you did not ignore either)?
Thanks, but I think the semantics of git stash is pretty well defined.
And it means that you stash away _tracked_ content that was not yet
committed.
I mean, you can have your desired behaviour with
$ git add .
$ git stash
but if we were to fulfil your wish and change the default behaviour, there
is no way back to the current behaviour (which I happen to find pretty
sane).
Ciao,
Dscho
next prev parent reply other threads:[~2007-09-29 21:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 18:27 Stashing untracked files Neil Macneale
2007-09-29 21:03 ` Johannes Schindelin
2007-09-29 21:10 ` Benoit SIGOURE
2007-09-29 21:46 ` Neil Macneale
2007-09-29 22:00 ` Johannes Schindelin
2007-09-30 3:59 ` Neil Macneale
2007-09-30 8:41 ` Steffen Prohaska
2007-09-30 13:18 ` Wincent Colaiuta
2007-09-29 21:51 ` Johannes Schindelin [this message]
2007-09-29 22:23 ` Tom Prince
2007-09-29 23:09 ` Johannes Schindelin
2007-09-30 20:44 ` Tom Tobin
2007-09-30 21:25 ` Johannes Schindelin
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=Pine.LNX.4.64.0709292248400.28395@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mac4-git@theory.org \
--cc=tsuna@lrde.epita.fr \
/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).