{"thread":{"id":"8649","subject":"Suggestions for documentation","startedAt":"2007-06-19T07:33:05Z","lastAt":"2007-06-21T15:16:09Z","messageCount":5,"participants":["Claudio Scordino","Johannes Schindelin","Luiz Fernando N. Capitulino","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"45324","messageId":"467786B1.5000009@gmail.com","threadId":"8649","inReplyTo":null,"subject":"Suggestions for documentation","fromName":"Claudio Scordino","fromEmail":"cloud.of.andor@gmail.com","sentAt":"2007-06-19T07:33:05Z","receivedAt":"2007-06-19T07:33:05Z","isPatch":false,"sender":{"key":"cloud.of.andor@gmail.com","avatar":null},"body":"Hi,\n\n I just want to suggest to put some missing information in the git manpages.\n\n1) As my previous question shown, how to clone from a specified port is not \ncurrently documented. You should just add a sentence saying that the command is\n\ngit clone git://server:port/path/\n\n2) Maybe it is better to highlight that after a push on a remote repository, the \nuser has to do a checkout on that repository (people from the CVS and SVN worlds \nget easily confused, otherwise).\n\nMoreover (and I did not fully understood why) if I just use \"git checkout\" \nwithout the -f option, I cannot see the changes that have been pushed from the \ncloned repository.\n\nRegards,\n\n Claudio\n"},{"id":"45335","messageId":"Pine.LNX.4.64.0706191043170.4059@racer.site","threadId":"8649","inReplyTo":"467786B1.5000009@gmail.com","subject":"Re: Suggestions for documentation","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-06-19T09:47:53Z","receivedAt":"2007-06-19T09:47:53Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Tue, 19 Jun 2007, Claudio Scordino wrote:\n\n> 1) As my previous question shown, how to clone from a specified port is not\n> currently documented. You should just add a sentence saying that the command\n> is\n> \n> git clone git://server:port/path/\n\nI thought this was quite standard with other protocol? I.e. \nhttp://host:port/path is what I do all the time.\n\nHaving said that, this should be relatively easy? Want to give it a try?\n\n> 2) Maybe it is better to highlight that after a push on a remote \n> repository, the user has to do a checkout on that repository (people \n> from the CVS and SVN worlds get easily confused, otherwise).\n\nThat has been discussed on and off, and I think that you are not using a \nvalid workflow here. If you are pushing into another repo, _by definition_ \nyou do not have a work tree to resolve conflicts with.\n\nThus, you should rather do something like \"push upstream \nmaster:refs/heads/push\" on the pushing side, and \"merge push\" on the other \nside.\n\nIt is a common behaviour by former CVS users (I did the same!), but it is \nfixable.\n\n> Moreover (and I did not fully understood why) if I just use \"git \n> checkout\" without the -f option, I cannot see the changes that have been \n> pushed from the cloned repository.\n\nSame reason. This is not a valid workflow. You kind of changed the tip of \nthe branch in the pushed-to repo behind its back. The only way to make \nthis work that I am aware of is \"git read-tree -m -u HEAD\", but as I \nstated before, you probably want to change the way you're working.\n\nHth,\nDscho\n"},{"id":"45445","messageId":"20070620180615.529dff2a@localhost","threadId":"8649","inReplyTo":"467786B1.5000009@gmail.com","subject":"Re: Suggestions for documentation","fromName":"Luiz Fernando N. Capitulino","fromEmail":"lcapitulino@mandriva.com.br","sentAt":"2007-06-20T21:06:15Z","receivedAt":"2007-06-20T21:06:15Z","isPatch":false,"sender":{"key":"lcapitulino@mandriva.com.br","avatar":null},"body":"Em Tue, 19 Jun 2007 09:33:05 +0200\nClaudio Scordino escreveu:\n\n| Hi,\n| \n| I just want to suggest to put some missing information in the git manpages.\n| \n| 1) As my previous question shown, how to clone from a specified port is not \n| currently documented. You should just add a sentence saying that the command is\n| \n| git clone git://server:port/path/\n| \n| 2) Maybe it is better to highlight that after a push on a remote repository, the \n| user has to do a checkout on that repository (people from the CVS and SVN worlds \n| get easily confused, otherwise).\n| \n| Moreover (and I did not fully understood why) if I just use \"git checkout\" \n| without the -f option, I cannot see the changes that have been pushed from the \n| cloned repository.\n\n git-rebase documentation needs some change too. We should add some high level\ndescription in one paragraph at the top of the file.\n\n I answer the very same question ('why should I want to use git-rebase?')\nthree times per week.\n\n I'll submit a patch shortly.\n\n-- \nLuiz Fernando N. Capitulino\n"},{"id":"45485","messageId":"467A5FE1.1010401@gmail.com","threadId":"8649","inReplyTo":"20070620180615.529dff2a@localhost","subject":"Re: Suggestions for documentation","fromName":"Claudio Scordino","fromEmail":"cloud.of.andor@gmail.com","sentAt":"2007-06-21T11:24:17Z","receivedAt":"2007-06-21T11:24:17Z","isPatch":false,"sender":{"key":"cloud.of.andor@gmail.com","avatar":null},"body":"Hi,\n\n actually I didn't understand the difference between \"git clone --bare\" and\n\"git --bare fetch\" either... (maybe is not clear in the documentation ?)\n\nFor instance, what should be used when setting up a public not-working repository ?\n\nI mean, we can use both\n\ngit --bare init\ngit --bare fetch ... master:master\n\nand\n\ngit clone --bare ...\n\nThank you in advance.\n\nRegards,\n\n Claudio\n\n\n\nLuiz Fernando N. Capitulino wrote:\n> Em Tue, 19 Jun 2007 09:33:05 +0200\n> Claudio Scordino escreveu:\n> \n> | Hi,\n> | \n> | I just want to suggest to put some missing information in the git manpages.\n> | \n> | 1) As my previous question shown, how to clone from a specified port is not \n> | currently documented. You should just add a sentence saying that the command is\n> | \n> | git clone git://server:port/path/\n> | \n> | 2) Maybe it is better to highlight that after a push on a remote repository, the \n> | user has to do a checkout on that repository (people from the CVS and SVN worlds \n> | get easily confused, otherwise).\n> | \n> | Moreover (and I did not fully understood why) if I just use \"git checkout\" \n> | without the -f option, I cannot see the changes that have been pushed from the \n> | cloned repository.\n> \n> git-rebase documentation needs some change too. We should add some high level\n> description in one paragraph at the top of the file.\n> \n> I answer the very same question ('why should I want to use git-rebase?')\n> three times per week.\n> \n> I'll submit a patch shortly.\n> \n"},{"id":"45506","messageId":"f5e4no$b6f$1@sea.gmane.org","threadId":"8649","inReplyTo":"467A5FE1.1010401@gmail.com","subject":"Re: Suggestions for documentation","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2007-06-21T15:16:09Z","receivedAt":"2007-06-21T15:16:09Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Claudio Scordino wrote:\n\n>     actually I didn't understand the difference between \"git clone --bare\" and\n> \"git --bare fetch\" either... (maybe is not clear in the documentation ?)\n> \n> For instance, what should be used when setting up a public not-working repository ?\n> \n> I mean, we can use both\n> \n> git --bare init\n> git --bare fetch ... master:master\n\n\"git --bare \" is equivalent to \"git --git-dir=. \", and\nit only tells where to find repository...\n \n> and\n> \n> git clone --bare  ...\n\n...while \"git clone --bare\" setups _bare_ repository, which means\n1:1 mapping of references, and no working area.\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"}]}