Hi, On Tue, 19 Jun 2007, Claudio Scordino wrote: > 1) As my previous question shown, how to clone from a specified port is not > currently documented. You should just add a sentence saying that the command > is > > git clone git://server:port/path/ I thought this was quite standard with other protocol? I.e. http://host:port/path is what I do all the time. Having said that, this should be relatively easy? Want to give it a try? > 2) Maybe it is better to highlight that after a push on a remote > repository, the user has to do a checkout on that repository (people > from the CVS and SVN worlds get easily confused, otherwise). That has been discussed on and off, and I think that you are not using a valid workflow here. If you are pushing into another repo, _by definition_ you do not have a work tree to resolve conflicts with. Thus, you should rather do something like "push upstream master:refs/heads/push" on the pushing side, and "merge push" on the other side. It is a common behaviour by former CVS users (I did the same!), but it is fixable. > Moreover (and I did not fully understood why) if I just use "git > checkout" without the -f option, I cannot see the changes that have been > pushed from the cloned repository. Same reason. This is not a valid workflow. You kind of changed the tip of the branch in the pushed-to repo behind its back. The only way to make this work that I am aware of is "git read-tree -m -u HEAD", but as I stated before, you probably want to change the way you're working. Hth, Dscho - 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
