From: "Felipe Contreras" <felipe.contreras@gmail.com>
To: "Santi Béjar" <santi@agolina.net>
Cc: "Jakub Narebski" <jnareb@gmail.com>, "git list" <git@vger.kernel.org>
Subject: Re: Git weekly news: 2008-49
Date: Fri, 5 Dec 2008 23:57:26 +0200 [thread overview]
Message-ID: <94a0d4530812051357m4f0bc591n802c41a78e698b3b@mail.gmail.com> (raw)
In-Reply-To: <adf1fd3d0812051344x79fe2c10i77b2abb8e7e19fe@mail.gmail.com>
On Fri, Dec 5, 2008 at 11:44 PM, Santi Béjar <santi@agolina.net> wrote:
> 2008/12/5 Felipe Contreras <felipe.contreras@gmail.com>:
>> On Fri, Dec 5, 2008 at 6:02 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>
> [...]
>
>>>> But here are the links anyway. The order is rather random.
>>>
>>> Moreover the _quality_ of those links is very random.
>>
>> Exactly, I didn't choose them, that's what people have been tagging as
>> "git" in delicious.com. I'm subscribed to the RSS feed and saving the
>> ones that appear a lot.
>>
>> In fact I don't like some of them, but that's what the "public" finds
>> interesting.
>
> So I don't see the value of such a list. You can go to delicious and
> get it.
Try it. You can't see which ones are new, which are completely
irrelevant. There are duplicates and you can't see the popularity /
freshness ratio, or "hotness", never mind the most popular this week.
Apparently some people already found interesting links they haven't
seen before, so at lest there's value for them.
> Another thing that could be great is filtering this list to
> those that pass a certain criteria (mainly quality, up to date, ...)
> and present it in an attractive way, with summaries, categorized by
> type (trick, tutorial, comparison,...), ...
Yes, I'll probably improve the presentation.
--
Felipe Contreras
next prev parent reply other threads:[~2008-12-05 21:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 0:43 Git weekly news: 2008-49 Felipe Contreras
2008-12-05 16:02 ` Jakub Narebski
2008-12-05 17:00 ` Michael J Gruber
2008-12-05 17:46 ` Felipe Contreras
2008-12-05 19:27 ` Jakub Narebski
2008-12-05 21:44 ` Santi Béjar
2008-12-05 21:57 ` Felipe Contreras [this message]
2008-12-05 22:11 ` Santi Béjar
2008-12-05 20:54 ` Junio C Hamano
2008-12-05 21:49 ` Felipe Contreras
2008-12-05 22:33 ` Jakub Narebski
2008-12-06 3:53 ` Casual observers (was Re: Git weekly news: 2008-49) Jean-Rene David
2008-12-06 5:53 ` Edward Z. Yang
2008-12-06 6:52 ` Boyd Stephen Smith Jr.
2008-12-05 21:12 ` Git weekly news: 2008-49 Nanako Shiraishi
2008-12-05 22:18 ` Nanako Shiraishi
2008-12-05 22:42 ` Junio C Hamano
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=94a0d4530812051357m4f0bc591n802c41a78e698b3b@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=santi@agolina.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).