From: Claudio Scordino <cloud.of.andor@gmail.com>
To: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
Cc: git@vger.kernel.org, Johannes.Schindelin@gmx.de
Subject: Re: Suggestions for documentation
Date: Thu, 21 Jun 2007 13:24:17 +0200 [thread overview]
Message-ID: <467A5FE1.1010401@gmail.com> (raw)
In-Reply-To: <20070620180615.529dff2a@localhost>
Hi,
actually I didn't understand the difference between "git clone --bare" and
"git --bare fetch" either... (maybe is not clear in the documentation ?)
For instance, what should be used when setting up a public not-working repository ?
I mean, we can use both
git --bare init
git --bare fetch ... master:master
and
git clone --bare ...
Thank you in advance.
Regards,
Claudio
Luiz Fernando N. Capitulino wrote:
> Em Tue, 19 Jun 2007 09:33:05 +0200
> Claudio Scordino <cloud.of.andor@gmail.com> escreveu:
>
> | Hi,
> |
> | I just want to suggest to put some missing information in the git manpages.
> |
> | 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/
> |
> | 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).
> |
> | 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.
>
> git-rebase documentation needs some change too. We should add some high level
> description in one paragraph at the top of the file.
>
> I answer the very same question ('why should I want to use git-rebase?')
> three times per week.
>
> I'll submit a patch shortly.
>
next prev parent reply other threads:[~2007-06-21 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 7:33 Suggestions for documentation Claudio Scordino
2007-06-19 9:47 ` Johannes Schindelin
2007-06-20 21:06 ` Luiz Fernando N. Capitulino
2007-06-21 11:24 ` Claudio Scordino [this message]
2007-06-21 15:16 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=467A5FE1.1010401@gmail.com \
--to=cloud.of.andor@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=lcapitulino@mandriva.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).