From: Junio C Hamano <junkio@cox.net>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Check and document the options to prevent mistakes.
Date: Wed, 21 Jun 2006 20:45:45 -0700 [thread overview]
Message-ID: <7v1wthyhsm.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <m1irmt6gax.fsf@ebiederm.dsl.xmission.com> (Eric W. Biederman's message of "Wed, 21 Jun 2006 21:05:26 -0600")
ebiederm@xmission.com (Eric W. Biederman) writes:
> Junio C Hamano <junkio@cox.net> writes:
>
>> Does it grok '"Biederman, Eric W." <eb@xm.com>' some people seem
>> to do properly, or do we care (I personally don't)?
>
> Nope. If figure that is lesser of two evils.
Fair enough.
prev parent reply other threads:[~2006-06-22 3:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 13:17 [PATCH] Check and document the options to prevent mistakes Eric W. Biederman
2006-06-21 20:53 ` Junio C Hamano
2006-06-22 3:05 ` Eric W. Biederman
2006-06-22 3:45 ` Junio C Hamano [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=7v1wthyhsm.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=ebiederm@xmission.com \
--cc=git@vger.kernel.org \
/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).