From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Subject: [PATCH 0/2] Handle cvsimport config for uppercase options
Date: Wed, 29 Dec 2010 22:55:32 +0100 [thread overview]
Message-ID: <cover.1293659350.git.git@drmicha.warpmail.net> (raw)
Sorry for rushing this out (no in-reply-to etc.) , I'm mostly offline
these days and pressed by the rc phase.
This is the version (n+1) as suggested by Junio, so 2/2 is mostly by JC
(only that his patch didn't apply, it probably was for maint).
I dropped the documentation patch, since the discussion resulted in short
config option names being frowned upon, so we should leave them undocumented
and return to rewrite them one day.
Michael J Gruber (2):
cvsimport: partial whitespace cleanup
cvsimport: handle the parsing of uppercase config options
git-cvsimport.perl | 33 +++++++++++++++++++++++++--------
t/t9600-cvsimport.sh | 7 +++++--
2 files changed, 30 insertions(+), 10 deletions(-)
--
1.7.3.4.865.ga2bc4
next reply other threads:[~2010-12-29 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 21:55 Michael J Gruber [this message]
2010-12-29 21:55 ` [PATCH 1/2] cvsimport: partial whitespace cleanup Michael J Gruber
2010-12-29 21:55 ` [PATCH 2/2] cvsimport: handle the parsing of uppercase config options Michael J Gruber
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=cover.1293659350.git.git@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--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).