Scott O, Thanks for posting this reply! I just now started using Git and
its command line interface. I wondered how to get the "warning: LF will be
replaced by CRLF in..." to quit nagging me.
On Monday, June 7, 2010 6:01:42 PM UTC-5, Scott O wrote:
> I have a remote repository (at Assembla.com) for a virtual
> collaborative project. I'm using the version of git available via apt-
> get for ubuntu: 220.127.116.11. I have used Git for few months
> After the last commit, it now seems very broken. While on that commit
> it shows 4 files as changed that have not been changed. If I 'git
> reset --hard', there is no effect, the files are still shown as
> changed. If I 'git checkout <filename>' one of the files, no effect.
> If I clone the repository anew, it shows about 100 files as changed in
> the master branch (different branch from above). Most of these are
> cloned local repository. Same behavior by reset --hard and checkout as
> above: no effect. Here's reset:
> $ git reset --hard
> HEAD is now at 7145157 Neighborhoods list is a one-column list in new
> service offering page
> $ git st
> # On branch master
> # Changed but not updated:
> # (use "git add <file>..." to update what will be committed)
> # (use "git checkout -- <file>..." to discard changes in working
> # modified:
> ....many more files
> 'git fsck' gives no output.
> I even did a 'git gc' on my local repository, push it to a new remote
> repository and cloned that. The problem is still there!
> WTF is going on? I'm losing my mind.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.