From: Jeff King <peff@peff.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: [PATCH] git(1): remove a defunct link to "list of authors"
Date: Sat, 8 Dec 2012 06:02:53 -0500 [thread overview]
Message-ID: <20121208110253.GA24518@sigill.intra.peff.net> (raw)
In-Reply-To: <CAJo=hJsT+ChAr8vLQ99QPyrCXYAtuEUWn5Wdb-k1brBxk6V45A@mail.gmail.com>
On Fri, Dec 07, 2012 at 01:09:51PM -0800, Shawn O. Pearce wrote:
> On Fri, Dec 7, 2012 at 9:59 AM, Junio C Hamano <gitster@pobox.com> wrote:
> > Junio C Hamano <gitster@pobox.com> writes:
> >
> >> The linked page has not been showing the promised "more complete
> >> list" for more than 6 months by now, and nobody has resurrected
> >> the list there nor elsewhere since then.
> >>
> >> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> >> ---
> >> * If somebody has a working replacement URL, we could use that
> >> instead, of course. Takers?
> >
> > A possible alternative could be https://www.ohloh.net/p/git/contributors/summary
>
> Eh, I think just removing the link is sufficient.
FYI, I just submitted a patch to add a contributors page to git-scm.com
that looks similar to the old one. That patch being the sum total of my
ruby and rails experience, I'd expect some re-working to be necessary
before it is merged:
https://github.com/github/gitscm-next/pull/216
So it probably makes sense to go ahead and drop the link from the
manpage for now, and we can re-add it if the contributors page gets
merged (in my patch, it has a different path, so we would need to tweak
the URL eventually anyway).
-Peff
next prev parent reply other threads:[~2012-12-08 11:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 17:54 [PATCH] git(1): remove a defunct link to "list of authors" Junio C Hamano
2012-12-07 17:59 ` Junio C Hamano
2012-12-07 21:09 ` Shawn Pearce
2012-12-08 11:02 ` Jeff King [this message]
2012-12-09 13:29 ` Nguyen Thai Ngoc Duy
2012-12-10 6:31 ` Junio C Hamano
2012-12-10 12:04 ` Nguyen Thai Ngoc Duy
2012-12-12 12:24 ` Jeff King
2012-12-12 18:06 ` Junio C Hamano
2012-12-13 12:25 ` 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=20121208110253.GA24518@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.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).