From: "Felipe Contreras" <felipe.contreras@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: "git list" <git@vger.kernel.org>
Subject: Re: Git weekly news: 2008-49
Date: Fri, 5 Dec 2008 19:46:20 +0200 [thread overview]
Message-ID: <94a0d4530812050946r5ea7ddb2v1d93d28ba679813b@mail.gmail.com> (raw)
In-Reply-To: <m3d4g6ipah.fsf@localhost.localdomain>
On Fri, Dec 5, 2008 at 6:02 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> "Felipe Contreras" <felipe.contreras@gmail.com> writes:
>
>> Hi there,
>>
>> I've been following the git tag at delicious.com[1] and there's quite
>> many interesting links, so I thought on gathering them so the git
>> community can enjoy them in one pack :)
>
> Nice work, although I think better alternative would be to weed those
> links out, and put them in appropriate sections (or subsections) on
> Git Wiki; to be more exact on http://git.or.cz/gitwiki/GitLinks
Right, but next week the links will be different. This time the links
where not really from this week, but they will be on the next
iterations.
Somebody could pick the relevant links and add them in the wiki.
>> The blog post is here:
>> http://gitlog.wordpress.com/2008/12/05/git-weekely-news-2008-49/
>
> First, "Official git blog"? Official? There is nothing official about
> it. "Unofficial git blog", or "A git developer blog" (or "A git
> follower blog"; unfortunately names like gitter or gitster for git
> power user's, like TeXnician for TeX users, are taken by nicknames on
> #git, if I remember correctly). Only git maintainer (Junio Hamano)
> and git development community (the git mailing list) can decide that
> something is "official" resource.
I asked in the mailing list and the only comment I got was: go ahead.
So yeah, that doesn't look like an "official" blessing, but it's not
bad either.
Anyway, my idea is that many gitsters will participate on this blog,
it's not my personal blog, I already have one.
Who wants an account?
> Second, I am a bit curious about 49 in "Git weekly news: 2008-49"
> name of the post.
It's the week number.
> Third, it is collection of links, not news[1].
True, "Git weekly links" sounds better?
> [1] It would be nice if somebody resurrected GitTraffic, offshot of
> now defunct KernelTraffic, or at least helped to write Git articles
> for KernelTrap (which currently is in a bit of hiatus).
>
>>
>> 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.
>> Why Git is Better than X
>> http://whygitisbetterthanx.com/
>
> Quite good link from what I superficially checked, present in
> GitComparison wiki page.
>
>>
>> GitTorrent, The Movie
>> http://www.advogato.org/article/994.html
>
> This article is so full of bad information, exaggeration and
> hyperbole, that it would be better to forget about it, and not put it
> in the list.
It's popular, and a lot of people find it interesting. /me shrugs
>> Peer-to-peer Protocol for Synchronizing of Git Repositories
>> http://code.google.com/p/gittorrent/
>
> Not news.
Right, but it is to many people.
<snip/>
Thanks for the comments, but gathering all these links is already
taking me more time that I wished.
> I have a host of links to blog posts with git or distributed version
> control info bookmarked...
My objective is to do this weekly. Maybe I'll put the links in a git
repo so people can see them before I make the post. Would you find
that useful?
As an example of possible links for next week:
My RubyGems development tools and workflow
http://drnicwilliams.com/2008/12/05/my-rubygems-development-tools-and-workflow/
Pushr, or the application will deploy itself
http://www.restafari.org/pushr-or-the-application-will-deploy-itself.html
--
Felipe Contreras
next prev parent reply other threads:[~2008-12-05 17:47 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 [this message]
2008-12-05 19:27 ` Jakub Narebski
2008-12-05 21:44 ` Santi Béjar
2008-12-05 21:57 ` Felipe Contreras
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=94a0d4530812050946r5ea7ddb2v1d93d28ba679813b@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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).