By the way,  this is what I get

C:\GITtest>git push --all
Counting objects: 29, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (24/24), done.
Writing objects: 100% (29/29), 25.24 KiB | 12.00 KiB/s, done.
Total 29 (delta 1), reused 0 (delta 0)
remote: error: refusing to update checked out branch: refs/heads/master
remote: error: By default, updating the current branch in a non-bare 
repository
remote: error: is denied, because it will make the index and work tree 
inconsistent
remote: error: with what you pushed, and will require 'git reset --hard' to 
match
remote: error: the work tree to HEAD.
remote: error:
remote: error: You can set 'receive.denyCurrentBranch' configuration 
variable to
remote: error: 'ignore' or 'warn' in the remote repository to allow pushing 
into
remote: error: its current branch; however, this is not recommended unless 
you
remote: error: arranged to update its work tree to match what you pushed in 
some
remote: error: other way.
remote: error:
remote: error: To squelch this message and still keep the default 
behaviour, set
remote: error: 'receive.denyCurrentBranch' configuration variable to 
'refuse'.
To //labuilds01/c$/GIT
 ! [remote rejected] master -> master (branch is currently checked out)
error: failed to push some refs to '//labuilds01/c$/GIT'

C:\GITtest>





On Thursday, March 12, 2015 at 4:42:36 PM UTC-7, William Lasiewicz wrote:
>
> I have been trying to set up get and have it actually work.
> So far pretty much crap.
>
> Here is what I do
> Set up a Git repository on my server
> Git Init
>
> From my machine,  I go a GIT Pull and point some directory
> I add some files to that directory
> GIT Submit, with some stupid comment so it works
> GIT Push,  this usually breaks and tells me it can't push because the 
> branch is checked out.
>
> All I want to do it create a repository on the server,  add some files 
> locally from my machine,  push and go to another machine and actually see 
> those files.
> In any other tool,  this is completly easy, but in GIT,  there is about a 
> 50% you are going to lose everything.  How in the hell can this be so 
> popular?
>

-- 
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 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to