From: Junio C Hamano <junkio@cox.net>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Sam Ravnborg <sam@ravnborg.org>, git@vger.kernel.org
Subject: Re: dumb transports not being welcomed..
Date: Tue, 13 Sep 2005 15:23:57 -0700 [thread overview]
Message-ID: <7vek7swqrm.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200509132203.j8DM3foH008451@laptop11.inf.utfsm.cl> (Horst von Brand's message of "Tue, 13 Sep 2005 18:03:41 -0400")
Horst von Brand <vonbrand@inf.utfsm.cl> writes:
> Junio C Hamano <junkio@cox.net> wrote:
>
> [...]
>
>> Using cogito is not a problem at all. The mechanism to prepare
>> trees to serve wider audience not being used widely is.
>
> It isn't really documented...
True. The existing documentation might be sketchy. We only
have the following documentation pages right now. Clarification
patches are welcome.
http://www.kernel.org/pub/software/scm/git/docs/tutorial.html
Look for "Publishing your work" section, and
"Working with Others section, "project lead" and "subsystem
maintainer" subsections, both bullet point #2.
http://www.kernel.org/pub/software/scm/git/docs/git-update-server-info.html
The above sections in the tutorial repeatedly mentions this
command.
http://www.kernel.org/pub/software/scm/git/docs/repository-layout.html
And git-update-server-info documentation refers to this page.
Look for "objects/info/packs" and "info/refs".
next prev parent reply other threads:[~2005-09-13 22:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 21:07 dumb transports not being welcomed Junio C Hamano
2005-09-13 21:14 ` Sam Ravnborg
2005-09-13 21:30 ` Junio C Hamano
2005-09-13 21:42 ` Sam Ravnborg
2005-09-13 22:03 ` Horst von Brand
2005-09-13 22:23 ` Junio C Hamano [this message]
2005-09-13 22:11 ` Junio C Hamano
2005-09-13 22:21 ` Jeff Garzik
2005-09-13 22:29 ` Junio C Hamano
2005-09-14 13:21 ` Jeff Garzik
2005-09-13 22:29 ` Linus Torvalds
2005-09-13 22:37 ` Junio C Hamano
2005-09-13 22:55 ` Linus Torvalds
2005-09-13 23:02 ` Junio C Hamano
2005-09-14 2:25 ` Kay Sievers
2005-09-14 3:32 ` Junio C Hamano
2005-09-14 0:01 ` Johannes Schindelin
2005-09-14 0:57 ` Linus Torvalds
2005-09-14 1:42 ` Linus Torvalds
2005-09-14 8:38 ` Johannes Schindelin
2005-09-14 15:07 ` Linus Torvalds
2005-09-15 9:17 ` Junio C Hamano
2005-09-14 10:45 ` Sven Verdoolaege
2005-09-14 16:14 ` Junio C Hamano
2005-09-14 14:10 ` Jon Loeliger
2005-09-14 19:00 ` Junio C Hamano
2005-09-14 19:13 ` Jon Loeliger
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=7vek7swqrm.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=vonbrand@inf.utfsm.cl \
/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).