Thread (9 messages) flat view 9 messages, 4 authors, 2016-06-15

Re: Corruption of branch?

From: Thomas Nyberg <hidden>
Date: 2016-06-15 23:07:27

wow right on the button. yeah i have the "frus" folder in the root of my 
repository. i never knew that git checkout also searches the root of the 
repository like that. it appears i'm a fool who doesn't read 
documentation...

i learned something knew and can move this from the "bizarre index 
corruption" category to the "user error" category. thanks so much everyone!

On 12/14/2015 03:40 PM, Dennis Kaarsemaker wrote:
On ma, 2015-12-14 at 15:33 -0500, Thomas Nyberg wrote:
quoted
What exactly are you looking for? Here's the results of the following
command:

$ git for-each-ref | grep frus
1750cba5a94b3fe6041aaf49de430a558a3b9bc8 commit
refs/heads/frus_body_cleaning
3a1dbe48299f6eda1cc4b69cab35284c0f0355eb commit	refs/remotes/o
rigin/frus
1750cba5a94b3fe6041aaf49de430a558a3b9bc8 commit
refs/remotes/origin/frus_body_cleaning

Sorry if this isn't what you're looking for. I'm actually not very
familiar with these different internal git commands...
This is what I was looking for. Unfortunately it doesn't show any of
the smoking guns I had hoped for.

That leaves only one option: you also have a file or directory named
'frus' in the root of your repository. In this case 'git checkout frus'
does the same as 'git checkout -- frus' instead of DWIM'ing 'git
checkout frus' to 'git checkout -b frus origin/frus'
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help