From: Kevin Geiss <kevin@desertsol.com>
To: Kevin Geiss <kevin@desertsol.com>
Cc: martin.langhoff@gmail.com, git@vger.kernel.org
Subject: Re: eth
Date: Mon, 14 Nov 2005 09:47:37 -0700 [thread overview]
Message-ID: <20051114164737.GG9131@raven.localdomain> (raw)
In-Reply-To: <20051114164047.GB9131@raven.localdomain>
oops, I munged up the subject on this one. I resent it with '1/1' in the subject. :(
On Mon, Nov 14, 2005 at 09:40:47AM -0700, Kevin Geiss wrote:
prev parent reply other threads:[~2005-11-14 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 16:40 eth Kevin Geiss
2005-11-14 16:45 ` [PATCH 1/1] git-cvsexportcommit.perl: Fix usage() output Kevin Geiss
2005-11-14 20:24 ` Kevin Geiss
2005-11-14 22:14 ` Junio C Hamano
2005-11-14 22:20 ` Martin Langhoff
2005-11-14 23:04 ` Junio C Hamano
2005-11-15 5:10 ` Martin Langhoff
2005-11-14 16:47 ` Kevin Geiss [this message]
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=20051114164737.GG9131@raven.localdomain \
--to=kevin@desertsol.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@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