git - How do I check if a repository is bare? -

I'm getting a warning

  Warning: You specify any referrals to push Not done, and current Remote Alert: Has not configured any Push Rispacex. The default action in this warning: Case is to push all the mailing to the Riffspec, that is, warnings of all branches: both of which are locally and remotely, will be updated. This can be a warning: Not necessarily what you want to do. WARNING: WARNING: You can specify the action you want to take in this matter, and warnings: 'push.default' to 'Warning:' Nothing: Do not push any warning: 'Milan': all existing branches (Default) WARNING: Push 'Tracking': Push the current branch to anyone who is tracking this warning: 'current': push the current branch  

(I think Is a warning that the remote is not bare, but still The purpose was to be a remote utility, and the directory (which is in foo.git ) does not have a .git directory. How do I check that it is useless?

Additional Information : On the remote repository computer, with git 1.5.4.3, and git in the local repository is 1.6.3.3. Both machines are Ubuntu - local is a Personnel Cola, Remote is an old version.

How do I check that it is useless?

As mentioned in (upvoted), if you have access to remote repos, then you can run in:

  git Rev-parse --is- Bare-repository  

It was launched (September 2007) and.

When the repositories are bare print "true", otherwise "wrong".

---

You can use (from):

  git config --add push.default current  
  
  git config --global push.default match  
 
 to specify how you want to push by default  < / Pre> 
 If you have many repositories 
 
 
 Present: Press the current branch in the branch of the same name. 
 
 
 Also check that an error message of warning did not come in this way. 
 
 
 Then your De Stanense repo can be a bare, but as stated in it: 
 
 
 When you  git pull  ,  fetch,   push  and some others you want to specify a  refspec  for the current repository. 
 A  Riffface  describes the mapping between the local context and the remote one, so that you can push (or drag) the master branch head and store it as your original branch head. You can. Basically it is a method of mapping branches between repo. See 
 
 
. 
 
 
 Note: This is true: 
 
 
 "Currently in the checked branch " Git push " will be rejected by default. 
 You receive the configuration variable  on the type of push received document.   
 But I do not think this is what you are seeing now.  
 
 As mentioned in "" (below)  
 
 To make this a "real" random repo, simply  .git , then  mv. GIT / * .; Rmdir .git .  Finally, edit the file named  config  and replace  bare = false  with  bare = true .  
 
 
 So if your destination repository is in the  config  file with  bare = true , then this is an unmatched repo is .