git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Urgent: Issue with GIT ...

From
KKKonstantin Khomoutov <flatworm@users.sourceforge.net>
Date
Jun 25, 2012, 13:29 UTC
Message-ID
<20120625172957.b73effa9.kostix@domain007.com>
In-Reply-To
<1340628925770-7562100.post@n2.nabble.com>

On Mon, 25 Jun 2012 05:55:25 -0700 (PDT) guruprasad <guruprasadkinI@gmail.com> wrote:

[...]
Show 10 quoted lines
> 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
[...]
Show 6 quoted lines
> 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.

This is covered in the Git FAQ [1] -- see the question «Why won't I see changes in the remote repo after "git push"?»

Supposedly you should either stick to pulling or start using a "reference" repository (some prefer to call it "central") as already suggested in [2]. In your case, I don't see why you really need pushes so I'd stick to pulling.

1. https://git.wiki.kernel.org/index.php/GitFaq
2. http://groups.google.com/group/git-users/msg/5b545f06510c7e2d
Previous: Angus HammondNext: Andy Hawkins
Message 6 of 10 in “Urgent: Issue with GIT ...”
  1. guruprasadJun 25, 2012
  2. Konstantin KhomoutovJun 25, 2012
  3. guruprasadJun 25, 2012
  4. jaseem abidJun 25, 2012
  5. Angus HammondJun 25, 2012
  6. Konstantin KhomoutovJun 25, 2012
  7. Andy HawkinsJun 25, 2012
  8. KevinJun 26, 2012
  9. Andy HawkinsJun 26, 2012
  10. KevinJun 26, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.