Hi, Maybe something like this? # git clone repo active # git clone repo beta # git clone repo new
In each of these local clones you can checkout the appropriate branch. If you modify one branch stuff push it back to the original repo # git push origin new Note that if you checked out the new branch in the repo you cloned from you will run into an error remote: error: refusing to update checked out branch: refs/heads/new 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 I think it would be best if the original repo is a bare repo to avoid above error https://git.wiki.kernel.org/index.php/GitFaq#How_do_I_make_existing_non-bare_repository_bare.3F -- Best, Markus On 16.Apr.2013, at 14:16, Rick Holt wrote: > I have three versions of my website which I update using ftp from my computer: > active - public version > beta - almost ready for public > new - experimental workplace > Currently, the three copies on my computer are soft linked to a git > repository and I switch among them using commit and checkout. > > [git repository]-----+---> [active image] -------ftp------> [active website] > | > +---> [beta image] -------ftp------> [beta website] > | > +---> [new image] -------ftp------> [new website] > > Unfortunately, this means before making a change in one branch, I have to > commit the current one and checkout another. This is > fraught with error possibilities, since it would be easy to forget which > branch I am currently in. > > So, is there a way to be able to work on all versions simultaneously as > separate branches? Could I have three copies of a git server repository, > each in its own branch, and work on them as if I were three developers on > three separate computers? > > [git repository]---------> [active image] -------ftp------> [active website] > > [git repository]---------> [beta image] -------ftp------> [beta website] > > [git repository]---------> [new image] -------ftp------> [new website] > > Rick. > > > -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
