From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: funeeldy <Marlene_Cote@affirmednetworks.com>
Cc: git@vger.kernel.org
Subject: Re: git checkout no longer warning about uncommitted/untracked files!
Date: Mon, 23 May 2011 22:37:17 +0200 [thread overview]
Message-ID: <4DDAC57D.9020809@lsrfire.ath.cx> (raw)
In-Reply-To: <1306171797211-6395441.post@n2.nabble.com>
Am 23.05.2011 19:29, schrieb funeeldy:
> I found some other posts that seem to indicate that this is the right place
> to file bug reports for git. If this is wrong, please let me know the
> proper method.
> We are using git version 1.7.3. We just noticed that git checkout no longer
> warns about uncommitted/untracked files and just deletes them!!!
I can't reproduce this behaviour based on this description alone:
$ git --version
git version 1.7.3
$ uname -a
Linux ubuntu 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011 i686 i686 i386 GNU/Linux
$ mkdir /tmp/repo && cd /tmp/repo
$ git init
Initialized empty Git repository in /tmp/repo/.git/
$ git config -l
color.ui=auto
user.name=René Scharfe
user.email=rene.scharfe@lsrfire.ath.cx
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
$ echo 1 >a
$ git add a
$ git commit -m.
[master (root-commit) b0e60d3] .
1 files changed, 1 insertions(+), 0 deletions(-)
create mode 100644 a
$ git branch x
$ echo uncommitted >a
$ echo untracked >b
$ git checkout x
M a
Switched to branch 'x'
$ cat a
uncommitted
$ cat b
untracked
Can you reconstruct what your colleague did, perhaps using his or
her shell's command history file (e.g. ~/.bash_history)?
next prev parent reply other threads:[~2011-05-23 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 17:29 git checkout no longer warning about uncommitted/untracked files! funeeldy
2011-05-23 20:37 ` René Scharfe [this message]
2011-05-23 21:10 ` Jeff King
2011-05-23 21:05 ` funeeldy
2011-05-23 21:17 ` funeeldy
2011-05-23 21:18 ` Jeff King
2011-05-23 21:27 ` Marlene Cote
2011-05-23 21:18 ` Jeff King
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=4DDAC57D.9020809@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=Marlene_Cote@affirmednetworks.com \
--cc=git@vger.kernel.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).