Re: git push from client is not updating files on server

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jerome Yanga <jerome.yanga@xxxxxxxxx> writes:

[jc: kicking the thread back to the list; I do not give free
consultation in private, but I do not mind answering questions in
public to help wider audience.]

> Thank you for the prompt response.
>
> The projects in the Apache DocumentRoot are bare repositories.  I
> think this is what allowed me to push at least this is how I
> understood it from the URL I had quoted in my last message.
>
> If I understood what you had said about push being the opposite of
> fetch, then it is understandable that the files on the working
> directory did not get updated and that it only shows in the Gitweb
> interface.
>
> So how do I make the changes go in the working tree?

By arranging a "checkout" to happen when you want to.  One common
way people seem to do this is to have "git reset --hard HEAD" in
post update hook when the push came to the current branch, assuming
that nobody but the update in response to "push" is expected to
touch the working tree of the receiving repository.

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]