From: Steven Noonan <steven@uplinklabs.net>
To: Nick Quaranto <nick@quaran.to>
Cc: git@vger.kernel.org
Subject: Re: git ready: daily git tips
Date: Sun, 8 Feb 2009 14:24:38 -0800 [thread overview]
Message-ID: <f488382f0902081424g47c75e3dr664d9f77b3558ffb@mail.gmail.com> (raw)
In-Reply-To: <1234131508141-2294642.post@n2.nabble.com>
On Sun, Feb 8, 2009 at 2:18 PM, Nick Quaranto <nick@quaran.to> wrote:
>
> I started this blog just around a month ago on a quest to learn more about
> git on a daily basis and to show others how awesome it is. If you have any
> suggestions on what content to cover or how things should be done
> differently, I would greatly appreciate it. Thanks!
>
> http://gitready.com
Heh, I've already got this in my RSS reader. It's got some pretty
awesome tips. I've learned more about git on there than pretty much
any other resource.
Keep up the good work. :)
- Steven
next prev parent reply other threads:[~2009-02-08 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 22:18 git ready: daily git tips Nick Quaranto
2009-02-08 22:24 ` Steven Noonan [this message]
2009-02-09 20:42 ` Nicolas Pitre
2009-02-10 1:20 ` Sitaram Chamarty
2009-02-10 10:19 ` Johannes Schindelin
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=f488382f0902081424g47c75e3dr664d9f77b3558ffb@mail.gmail.com \
--to=steven@uplinklabs.net \
--cc=git@vger.kernel.org \
--cc=nick@quaran.to \
/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).