From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
John Dlugosz <JDlugosz@TradeStation.com>,
git@vger.kernel.org, Avery Pennarun <apenwarr@gmail.com>,
Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: Re: ghost refs
Date: Fri, 9 Apr 2010 01:04:19 +0200 [thread overview]
Message-ID: <20100408230419.GA13704@vidovic> (raw)
In-Reply-To: <7vbpdt65ie.fsf@alter.siamese.dyndns.org>
The 08/04/10, Junio C Hamano wrote:
>
> We might want to have a general concensus on what we want to have in the
> documentation.
<...>
> I'll list my preference off the top of my head as a firestarter.
Nice. If a concensus is found for writing consistent documentation I
think it's worth to save in a file like Documentation/README or
Documentation/CONTRIBUTE.
--
Nicolas Sebrecht
next prev parent reply other threads:[~2010-04-08 23:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 16:38 ghost refs John Dlugosz
2010-04-07 16:58 ` Avery Pennarun
2010-04-07 21:00 ` Jeff King
2010-04-07 22:00 ` John Dlugosz
2010-04-07 22:03 ` Avery Pennarun
2010-04-07 22:10 ` John Dlugosz
2010-04-07 22:11 ` Avery Pennarun
2010-04-08 4:30 ` Jeff King
2010-04-08 16:07 ` John Dlugosz
2010-04-08 16:55 ` Junio C Hamano
2010-04-08 19:49 ` Jeff King
2010-04-08 20:42 ` Junio C Hamano
2010-04-08 22:14 ` Avery Pennarun
2010-04-08 23:04 ` Nicolas Sebrecht [this message]
2010-04-17 11:51 ` Jeff King
2010-04-17 16:32 ` Junio C Hamano
2010-04-17 16:57 ` Git documentation writing guidelines (was: Re: ghost refs) Jakub Narebski
2010-04-18 0:28 ` Git documentation writing guidelines Junio C Hamano
2010-04-19 15:33 ` ghost refs John Dlugosz
2010-04-20 7:02 ` Yann Dirson
2010-04-20 11:51 ` Jeff King
2010-04-20 12:02 ` Zefram
2010-04-20 13:00 ` Yann Dirson
2010-04-20 13:14 ` Zefram
2010-04-20 13:33 ` Jay Soffian
2010-04-20 14:24 ` Jeff King
2010-04-20 14:42 ` Yann Dirson
2010-04-20 14:52 ` Jay Soffian
2010-04-20 15:03 ` Alex Riesen
2010-04-20 15:10 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100408230419.GA13704@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=JDlugosz@TradeStation.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).