From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Jeff Garzik <jgarzik@pobox.com>, git@vger.kernel.org
Subject: Re: using-topic-branches.txt
Date: Mon, 19 Dec 2005 10:55:23 -0500 [thread overview]
Message-ID: <20051219155523.GC4147@fieldses.org> (raw)
In-Reply-To: <7v64plmz1e.fsf@assigned-by-dhcp.cox.net>
On Sun, Dec 18, 2005 at 09:33:17PM -0800, Junio C Hamano wrote:
> Jeff Garzik <jgarzik@pobox.com> writes:
>
> > master.kernel.org is non-public, so it shouldn't be mentioned in
> > documentation...
>
> I'm willing to be persuaded otherwise, but the reason I changed
> this part was twofold:
>
> - The documentation is meant to be an example for subsystem
> maintainers, who are "non-public" people anyway.
There are people without kernel.org accounts who do similar sorts of
work.
--b.
next prev parent reply other threads:[~2005-12-19 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 4:13 using-topic-branches.txt Brown, Len
2005-12-19 4:52 ` using-topic-branches.txt Jeff Garzik
2005-12-19 5:33 ` using-topic-branches.txt Junio C Hamano
2005-12-19 15:55 ` J. Bruce Fields [this message]
2005-12-19 22:24 ` using-topic-branches.txt H. Peter Anvin
2005-12-19 5:43 ` using-topic-branches.txt Junio C Hamano
2005-12-19 6:27 ` using-topic-branches.txt Linus Torvalds
2005-12-19 22:25 ` using-topic-branches.txt H. Peter Anvin
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=20051219155523.GC4147@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=jgarzik@pobox.com \
--cc=junkio@cox.net \
/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).