From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
git list <git@vger.kernel.org>
Subject: Re: Git weekly news: 2008-49
Date: Fri, 05 Dec 2008 18:00:54 +0100 [thread overview]
Message-ID: <49395E46.1030107@drmicha.warpmail.net> (raw)
In-Reply-To: <m3d4g6ipah.fsf@localhost.localdomain>
Jakub Narebski venit, vidit, dixit 05.12.2008 17:02:
> "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
>
>> 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.
>
> Second, I am a bit curious about 49 in "Git weekly news: 2008-49"
> name of the post.
Since it's "weekly" and this week is week number 49 in this year I have
a certain guess ;)
The blog has 2 entries only: That one and the wordpress welcome thingy...
>> Why Git is Better than X
>> http://whygitisbetterthanx.com/
>
> Quite good link from what I superficially checked, present in
> GitComparison wiki page.
Very nice indeed. Minor nitpick is comparing "hg add" to "git add" and
"hg commit" to "git commit -a", I'm discussing this with Scott already.
But very nice overall.
Cheers,
Michael
P.S.: For the record or in case anyone ?oogles this:
- compare "hg add" to "git add -N" and "hg commit" to "git commit -a",
which compares equivalent commands, or
- compare "hg add" to "git add" and "hg commit" to "git commit" (after
git add, but time "git commit" only), which compares similar sounding
commands; here, the sequence of commands is equivalent, just not the
individual ones
next prev parent reply other threads:[~2008-12-05 17:02 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 [this message]
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
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=49395E46.1030107@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=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).