From: Mike Ralphson <mike.ralphson@gmail.com>
To: Brent Goodrick <bgoodr@gmail.com>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: CR codes from git commands
Date: Thu, 22 Jan 2009 16:41:10 +0000 [thread overview]
Message-ID: <e2b179460901220841h17c9eda2h38e8baff2964dac3@mail.gmail.com> (raw)
In-Reply-To: <18808.39712.351656.138702@hungover.brentg.com>
2009/1/22 Brent Goodrick <bgoodr@gmail.com>:
> Mike Ralphson writes:
> > I think this earlier discussion is probably relevant... I'm guessing
> > though, $EDITOR is set correctly here 8-)
>
> I do have EDITOR set to a home-built version of gnuclient...
Sorry, I was being too subtle. My $EDITOR is set to vim, as god intended. 8-)
Mike
next prev parent reply other threads:[~2009-01-22 16:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 16:26 CR codes from git commands Brent Goodrick
2009-01-20 17:08 ` Johannes Schindelin
[not found] ` <18806.44057.477379.215492@hungover.brentg.com>
[not found] ` <alpine.DEB.1.00.0901210930370.7929@racer>
2009-01-21 14:42 ` Brent Goodrick
2009-01-21 15:38 ` Johannes Schindelin
2009-01-22 4:00 ` Brent Goodrick
2009-01-22 4:47 ` Daniel Barkalow
2009-01-22 7:34 ` Brent Goodrick
2009-01-22 7:46 ` Daniel Barkalow
2009-01-22 8:04 ` Junio C Hamano
2009-01-22 10:04 ` Mike Ralphson
2009-01-22 16:13 ` Brent Goodrick
2009-01-22 16:41 ` Mike Ralphson [this message]
2009-01-22 16:50 ` Johannes Schindelin
2009-01-22 16:44 ` Daniel Barkalow
2009-01-22 16:52 ` Johannes Schindelin
2009-01-23 16:12 ` Brent Goodrick
2009-01-23 16:59 ` Junio C Hamano
2009-01-23 18:41 ` Johannes Schindelin
2009-01-24 20:54 ` Brent Goodrick
2009-01-24 21:14 ` Johannes Schindelin
2009-01-25 9:19 ` Boyd Stephen Smith Jr.
2009-01-25 18:47 ` Brent Goodrick
2009-02-02 7:09 ` Brent Goodrick
2009-01-25 20:35 ` The lifecycle of a patch and the maintainer involvement 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=e2b179460901220841h17c9eda2h38e8baff2964dac3@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--cc=barkalow@iabervon.org \
--cc=bgoodr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).