From: Claudio Scordino <cloud.of.andor@gmail.com>
To: git@vger.kernel.org
Subject: Suggestions for documentation
Date: Tue, 19 Jun 2007 09:33:05 +0200 [thread overview]
Message-ID: <467786B1.5000009@gmail.com> (raw)
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.
Regards,
Claudio
next reply other threads:[~2007-06-19 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 7:33 Claudio Scordino [this message]
2007-06-19 9:47 ` Suggestions for documentation Johannes Schindelin
2007-06-20 21:06 ` Luiz Fernando N. Capitulino
2007-06-21 11:24 ` Claudio Scordino
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=467786B1.5000009@gmail.com \
--to=cloud.of.andor@gmail.com \
--cc=git@vger.kernel.org \
/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).