From: Yves Goergen <nospam.list@unclassified.de>
To: Holger Hellmuth <hellmuth@ira.uka.de>
Cc: git@vger.kernel.org
Subject: Re: Bug? Git checkout fails with a wrong error message
Date: Fri, 13 Jan 2012 18:46:07 +0100 [thread overview]
Message-ID: <4F106DDF.4040408@unclassified.de> (raw)
In-Reply-To: <4F1028AD.9080701@ira.uka.de>
On 13.01.2012 13:50 CE(S)T, Holger Hellmuth wrote:
> Important information missing: What version of git are you using? Should
> the version number begin with 1.6 or even lower you will get the advice
> to update your version to something non-ancient. Lots of bug-fixes
> happened in-between.
The first bug happened with msysGit 1.7.6 and 1.7.8, the second one
(reported now) with 1.7.8. That update didn't change a thing.
> I assume .cs is a C source file for visual studio, not a generated file,
> right ?
.cs is C# code and .Designer.cs files are used internally by the Visual
Studio designer. They're not supposed to be edited by the programmer and
contain lots of stuff that changes all the time. So they are generated
and presented in a different way.
> git does not record renames like cvs/svn do. It operates on snapshots
> and infers renames through comparisions. So if the next commit has a
> file missing and the same or similar file contents under some different
> path, it reports it as a rename. You can try -M with git log or git diff
> so that git expends more effort to detect renames+edits. Or you could
> avoid doing renames and edits of the same file in the same commit.
I renamed the file and created a new one with the same name. Is it so
simple to crash the Git repository?
>> -----
>> git.exe checkout form-refactoring
>>
>> Aborting
>> error: The following untracked working tree files would be overwritten by
>> checkout:
>> Form1.Designer.cs
>> Please move or remove them before you can switch branches.
>> -----
>
> You didn't mention that filename before (please assume people not
> accustomed to the ways of Visual Studio 2010). Is that another file you
> renamed and created new in the form-refactoring branch?
Form1.cs, Form1.Designer.cs and Form1.resx all belong together and are
renamed atomically. If I rename "Form1" in the project, actually these 3
files are renamed on disk.
> What does git diff -- Form1.Designer.cs' say?
Nothing.
> What does 'git diff form-refactoring -- Form1.Designer.cs' say?
All lines deleted.
Will this message also appear on the mailing list where I posted my
first message with Gmane? (That's the only thing I've found on the
official Git website.)
--
Yves Goergen "LonelyPixel" <nospam.list@unclassified.de>
Visit my web laboratory at http://beta.unclassified.de
next prev parent reply other threads:[~2012-01-13 18:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 18:44 Bug? Git checkout fails with a wrong error message Yves Goergen
2012-01-13 12:50 ` Holger Hellmuth
2012-01-13 17:46 ` Yves Goergen [this message]
2012-01-13 19:28 ` Holger Hellmuth
2012-01-15 8:14 ` Yves Goergen
2012-01-16 11:07 ` Holger Hellmuth
2012-01-16 18:50 ` Yves Goergen
2012-01-16 19:09 ` Jeff King
2012-01-16 21:20 ` Yves Goergen
2012-01-16 21:27 ` Jeff King
2012-01-17 7:41 ` Yves Goergen
2012-01-16 19:17 ` Thomas Rast
[not found] ` <4F152767.9010104@unclassified.de>
2012-01-17 8:45 ` Thomas Rast
2012-01-17 17:56 ` Yves Goergen
2012-01-19 10:24 ` Thomas Rast
2012-01-16 21:18 ` Erik Faye-Lund
2012-01-16 18:58 ` Yves Goergen
2012-01-13 17:37 ` Bug! Git merge also " Yves Goergen
2012-01-13 17:50 ` Jeff King
2012-01-13 18:49 ` Yves Goergen
2012-01-13 18:54 ` Jeff King
2012-01-13 19:05 ` Yves Goergen
2012-01-13 17:56 ` Carlos Martín Nieto
2012-01-13 18:59 ` Yves Goergen
2012-01-13 19:34 ` Jakub Narebski
2012-01-15 8:17 ` Yves Goergen
2012-01-15 10:08 ` Jakub Narebski
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=4F106DDF.4040408@unclassified.de \
--to=nospam.list@unclassified.de \
--cc=git@vger.kernel.org \
--cc=hellmuth@ira.uka.de \
/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).