From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Suggestions for documentation
Date: Thu, 21 Jun 2007 17:16:09 +0200 [thread overview]
Message-ID: <f5e4no$b6f$1@sea.gmane.org> (raw)
In-Reply-To: 467A5FE1.1010401@gmail.com
Claudio Scordino wrote:
> 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
"git --bare <command>" is equivalent to "git --git-dir=. <command>", and
it only tells where to find repository...
> and
>
> git clone --bare ...
...while "git clone --bare" setups _bare_ repository, which means
1:1 mapping of references, and no working area.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2007-06-21 15:43 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
2007-06-21 15:16 ` Jakub Narebski [this message]
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='f5e4no$b6f$1@sea.gmane.org' \
--to=jnareb@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).