From: Junio C Hamano <gitster@pobox.com>
To: Andrew Ardill <andrew.ardill@gmail.com>
Cc: Jeff King <peff@peff.net>,
git@vger.kernel.org, "Eduardo D'Avila" <erdavila@gmail.com>
Subject: Re: Helping on Git development
Date: Thu, 15 Sep 2011 08:50:13 -0700 [thread overview]
Message-ID: <7v4o0dreiy.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAH5451n=yEYYb0jO85+5_0dkuupQA2_WLvnH-fwPESS1GWy4Sg@mail.gmail.com> (Andrew Ardill's message of "Thu, 15 Sep 2011 16:24:22 +1000")
Andrew Ardill <andrew.ardill@gmail.com> writes:
>> I am moderately averse to hardcoding that URL that is guaranteed not to
>> survive the maintainer change in our README file. The howto/maintain-git
>> document mentions the periodical "A note from the maintainer" posting to
>> the list that has the same text, which is a more appropriate reference.
>
> Would a link to the wiki be more appropriate? Perhaps even a 'getting
> started' page that collates information like this?
> ...
> When kernel.org comes back online I may have a go at creating such a
> page. Any thoughts?
"Getting started" that describes how they got started, collectively
maintained by people who got started recently, may serve as a good guide
for people who follow. And if it is done as a wiki, you are free to create
and update without asking permission from the community ;-).
next prev parent reply other threads:[~2011-09-15 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOz-D1JW8RSR8kVWhT7v-DCbWayU8KhbePJwWrWvJwbmueRezQ@mail.gmail.com>
2011-09-14 3:05 ` Helping on Git development Eduardo D'Avila
2011-09-14 5:16 ` Andrew Ardill
2011-09-14 18:29 ` Junio C Hamano
2011-09-14 21:32 ` Jonathan Nieder
2011-09-14 23:14 ` Jeff King
2011-09-14 23:34 ` Junio C Hamano
2011-09-15 0:08 ` Jeff King
2011-09-15 6:24 ` Andrew Ardill
2011-09-15 15:50 ` Junio C Hamano [this message]
2011-09-15 17:21 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v4o0dreiy.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=andrew.ardill@gmail.com \
--cc=erdavila@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).