From: Ted Pavlic <ted@tedpavlic.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git <git@vger.kernel.org>, gitster <gitster@pobox.com>
Subject: Re: [PATCH 2/2] completion: Get rid of tabbed indentation in comments. Replace with spaces.
Date: Fri, 06 Feb 2009 11:19:20 -0500 [thread overview]
Message-ID: <498C6308.1000700@tedpavlic.com> (raw)
In-Reply-To: <20090206161303.GP26880@spearce.org>
> I expected Junio to use my TAB line as-is. I find them amusing.
Oops. :( In the future, I'll leave such things as is. I just figured the
"Trivially" was a side comment, but the function was still the same.
> Thanks for fixing that ${X-} thing. I clearly missed it on the
> review of the ps1 stuff.
I would have missed it myself... but then after I did a git pull, I was
getting a bash error on every single prompt. That was annoying. :)
Thanks --
Ted
--
Ted Pavlic <ted@tedpavlic.com>
Please visit my ALS association page:
http://web.alsa.org/goto/tedpavlic
My family appreciates your support in the fight to defeat ALS.
next prev parent reply other threads:[~2009-02-06 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 15:46 [PATCH 0/2] completion: Fixes GIT_PS1_SHOWDIRTYSTATE problems Ted Pavlic
2009-02-06 15:46 ` [PATCH 1/2] completion: Fix GIT_PS1_SHOWDIRTYSTATE to prevent unbound variable errors Ted Pavlic
2009-02-06 15:46 ` [PATCH 2/2] completion: Get rid of tabbed indentation in comments. Replace with spaces Ted Pavlic
2009-02-06 15:58 ` Shawn O. Pearce
2009-02-06 16:05 ` [PATCH 1/2] completion: Fix GIT_PS1_SHOWDIRTYSTATE to prevent unbound variable errors Ted Pavlic
2009-02-06 16:05 ` [PATCH 2/2] completion: Get rid of tabbed indentation in comments. Replace with spaces Ted Pavlic
2009-02-06 16:13 ` Shawn O. Pearce
2009-02-06 16:19 ` Ted Pavlic [this message]
2009-02-06 23:32 ` Thomas Rast
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=498C6308.1000700@tedpavlic.com \
--to=ted@tedpavlic.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.