From: Angus Hammond <angusgh@gmail.com>
Date: Mon, 25 Jun 2012 13:14:32 GMT
Subject: Re: Urgent: Issue with GIT ...
Message-ID: <CAOBOgRb9bMHSmMrj2tw56U_eSYjR+93=9ryE9YOcCsX+mVYeRA@mail.gmail.com>
In-Reply-To: <1340628925770-7562100.post@n2.nabble.com>

On 25 June 2012 13:55, guruprasad <guruprasadkinI@gmail.com> wrote:
> 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

> 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.
>

I *THINK* the problem you're having is that the push to A updates the
repository itself, but doesn't update the working directory unless you
explicitly tell it to from machine A later on. This is why you got
that horrible long error message when you did the git push, git was
trying to stop you from creating a state where the repository and the
working directory were different.

It seems like the solution would be to checkout master on machine A
after you push, or even better, set up a bare repository somewhere on
one of the systems and arrange for both of the repositories you work
in to push/pull to that one.

Angus