From: funeeldy <Marlene_Cote@affirmednetworks.com>
To: git@vger.kernel.org
Subject: git checkout no longer warning about uncommitted/untracked files!
Date: Mon, 23 May 2011 10:29:57 -0700 (PDT) [thread overview]
Message-ID: <1306171797211-6395441.post@n2.nabble.com> (raw)
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 had a
developer lose a lot of work today because
they were not committing regularly (which they will do now), and because I
told them to perform the checkout believing that it would do as it has
always done, and warn about their modified and untracked new files.
I believe this is a bug. Is it fixed in a later release already? If so,
which release? You guys really need to get a bug tracking system like Jira
to allow the git user community to file bugs and feature requests!!!!
Thanks for your help.
--
View this message in context: http://git.661346.n2.nabble.com/git-checkout-no-longer-warning-about-uncommitted-untracked-files-tp6395441p6395441.html
Sent from the git mailing list archive at Nabble.com.
next reply other threads:[~2011-05-23 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 17:29 funeeldy [this message]
2011-05-23 20:37 ` git checkout no longer warning about uncommitted/untracked files! René Scharfe
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=1306171797211-6395441.post@n2.nabble.com \
--to=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).