Re: Urgent: Issue with GIT ...

[guruprasad <guruprasadkinI@gmail.com>]

Firstly, I apologize for staring subject with "Urgent" and thank you very
much for your time and response.

As i told in my post earlier i am very much new to GIT, I was bit confused
with the tests i went on. I am sorry for not describing it clearly in my
last post. 

1) Pull command is working fine with both the Linux box. Comp A can pull
updates from comp B, vise versa.

2) Push command is not working with both Linux box, command given below.
       git push A master/git push B master

3) When i tried above command first time got an error saying 
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 user@A:/home/user/workspace/TestProject/.git
 ! [remote rejected] master -> master (branch is currently checked out)
error: failed to push some refs to
'user@A:/home/user/workspace/TestProject/.git'

so i added receive.denyCurrentBranch = ignore into git config and tried
again. I dint get any error.

4) But, modified things in files did not get reflected. i tried to push from
A-->B and B-->A. both dint work.
5) Push command i tried after modifying file, staging and committing.

Please let me know if more information is required.

Yes, I posted the same question to the git-users ML. Sorry for not
mentioning it in my post.

Thanks,
Guruprasad


--
View this message in context: http://git.661346.n2.nabble.com/Urgent-Issue-with-GIT-tp7562097p7562100.html
Sent from the git mailing list archive at Nabble.com.