On your machine and the server make hard links from the folders in the repository to the destination folders, that way when you check out the latest version then both locations are updated. So have /home/carlo/dev.repo/.git /home/carlo/dev.repo/public_html/ linked to /home/carlo/public_html/ /home/carlo/dev.repo/applications/ linked to /home/carlo/ci/application you can then work in the same place as usual, but do your commits from the dev.repo folder. My $0.02 solution. -----Original Message----- From: git-owner@xxxxxxxxxxxxxxx [mailto:git-owner@xxxxxxxxxxxxxxx] On Behalf Of Carlo Trimarchi Sent: Tuesday, 12 July 2011 02:07 To: Allen Fogleson Cc: git@xxxxxxxxxxxxxxx Subject: Re: repository in different directories On 11 July 2011 16:01, Allen Fogleson <afogleson@xxxxxxxxx> wrote: > Why not just make /home/carlo the repository, it has all the right folder > structure, then from the server you can pull, or you can git archive when > ready to release and unarchive on the server because I'm working on different applications and I need a repository for each one of them Steve Muadib >Ah, and for wrong: how about using one repository and setting up >a commit hook to move files to final places? the commit hook should stay in the local or the remote machine? -- 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 ��.n��������+%������w��{.n��������n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�