git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Felipe Contreras" <felipe.contreras@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: "git list" <git@vger.kernel.org>
Subject: Re: Git weekly links: 2008-51
Date: Mon, 22 Dec 2008 05:04:52 +0200	[thread overview]
Message-ID: <94a0d4530812211904y5bcd8e48jfb7172c77aae900a@mail.gmail.com> (raw)
In-Reply-To: <m3ej02d3tq.fsf@localhost.localdomain>

On Sat, Dec 20, 2008 at 9:50 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> "Felipe Contreras" <felipe.contreras@gmail.com> writes:
>
>> This week tortoisegit stole the spotlight. Maybe there weren't many
>> other links, or maybe I failed to notice them. Also, many people liked
>> the comment of Linus Torvalds regarding C++ in git.
>>
>> blog version:
>> http://gitlog.wordpress.com/2008/12/20/git-weekly-links-2008-51/
>>
>> == Articles ==
>>
>> Re: [RFC] Convert builin-mailinfo.c to use The Better String Library.
>> Linus Torvalds creates some buzz
>> http://lwn.net/Articles/249460/
>
> A not countered counter:
> C++ is a horrible language
> http://skepticalmethodologist.wordpress.com/2008/12/17/c-is-a-horrible-language/
>
>> == General links ==
>>
>> tortoisegit
>> http://code.google.com/p/tortoisegit/
>
> What about "Git Extensions":
> https://sourceforge.net/projects/gitextensions/
> http://github.com/spdr870/gitextensions/
>
> And "TortoiseGit Challenge":
> http://github.com/blog/256-tortoisegit-challenge

I didn't see many people bookmarking those links, but I added them to
the blog post as your picks.

-- 
Felipe Contreras

  reply	other threads:[~2008-12-22  3:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-20 12:16 Git weekly links: 2008-51 Felipe Contreras
2008-12-20 19:50 ` Jakub Narebski
2008-12-22  3:04   ` Felipe Contreras [this message]
2008-12-21  2:37 ` 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=94a0d4530812211904y5bcd8e48jfb7172c77aae900a@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).