From: Jakub Narebski <jnareb@gmail.com>
To: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
Cc: git@vger.kernel.org
Subject: Re: git-mailsplit: add `mailsplit.keep-cr` configuration variable.
Date: Thu, 11 Feb 2010 10:35:54 -0800 (PST) [thread overview]
Message-ID: <m3k4uj8vts.fsf@localhost.localdomain> (raw)
In-Reply-To: <20100211181354.GC15028@scotty.home>
Subject should read start with '[PATCH 2/4] '.
"Stefan-W. Hahn" <stefan.hahn@s-hahn.de> writes:
> If using git-mailsplit in environments where files with dos and unix
> line ending stay in one repository mbox patches must be split with
> additional parameter '--keep-cr', because the behaviour of
> git-mailsplit have been changed in commit c2ca1d79.
>
> With this patch the behaviour of git-mailsplit can be set via
> configuration file.
>
> Signed-off-by: Stefan-W. Hahn <stefan.hahn@s-hahn.de>
> ---
[...]
> +mailsplit.keep-cr::
> + If true git-mailsplit will not remove `\r` from lines ending
> + with `\r\n`. See linkgit:git-mailsplit[1].
> +
The convention use by config variables is to have camelCase or
allsmallcase name (variable name and section name are case
insensitive), e.g.:
transfer.unpackLimit::
status.showUntrackedFiles::
sendemail.aliasfiletype::
repack.usedeltabaseoffset::
etc., with the only outlier being add.ignore-errors.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-02-11 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1265911741-14840-1-git-send-email-stefan.hahn@s-hahn.de>
2010-02-11 18:13 ` git-mailsplit: Show parameter '--keep-cr' in usage and documentation Stefan-W. Hahn
2010-02-11 18:13 ` git-mailsplit: add `mailsplit.keep-cr` configuration variable Stefan-W. Hahn
2010-02-11 18:35 ` Jakub Narebski [this message]
2010-02-11 20:36 ` Junio C Hamano
2010-02-11 18:14 ` git-am: Add command line parameter `--keep-cr` passing it to git-mailsplit Stefan-W. Hahn
2010-02-11 18:14 ` Adding test for `--keep-cr` for git-mailsplit and git-am Stefan-W. Hahn
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=m3k4uj8vts.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=stefan.hahn@s-hahn.de \
/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).