From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Michael Somos <somos@grail.cba.csuohio.edu>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-1.4.0 make problems
Date: Sun, 18 Jun 2006 00:11:01 +0200 [thread overview]
Message-ID: <44947DF5.7080905@lsrfire.ath.cx> (raw)
In-Reply-To: <200606171016.k5HAGQ1D005560@grail.cba.csuohio.edu>
Michael Somos wrote:
> A good suggestion, but I am a newbie as you can tell, and would prefer to
> play in a sandbox for some time before I would attempt it.
You already sent a diff in your first message, so you're not that much
of a newbie. :-)
Thanks for telling us about your first encounter with git, by the way.
Take your time, and have fun learning and using git!
René
next prev parent reply other threads:[~2006-06-17 22:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 10:16 git-1.4.0 make problems Michael Somos
2006-06-17 13:09 ` Dennis Stosberg
2006-06-17 14:46 ` Michael Somos
2006-06-17 15:02 ` [PATCH] Make t4101-apply-nonl bring along its patches Dennis Stosberg
2006-06-17 22:11 ` Rene Scharfe [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-17 2:18 git-1.4.0 make problems Michael Somos
2006-06-17 6:58 ` Rene Scharfe
2006-06-17 20:56 ` Junio C Hamano
2006-06-17 21:55 ` Rene Scharfe
2006-06-17 22:40 ` 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=44947DF5.7080905@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=somos@grail.cba.csuohio.edu \
/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).