From: larsxschneider@gmail.com
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net, Johannes.Schindelin@gmx.de,
jehan@orb.com, whee@smaertness.net, me@ttaylorr.com,
Lars Schneider <larsxschneider@gmail.com>
Subject: [PATCH v1 0/2] convert: add alias support for 'working-tree-encoding' attributes
Date: Sun, 8 Jul 2018 20:30:34 +0200 [thread overview]
Message-ID: <20180708183036.29459-1-larsxschneider@gmail.com> (raw)
From: Lars Schneider <larsxschneider@gmail.com>
Hi,
this series adds Git config based alias support for
'working-tree-encoding' attributes that were introduced in 107642fe26
("convert: add 'working-tree-encoding' attribute", 2018-04-15).
The feature was suggested by Steve Groeger in [1].
The first patch is a refactoring with no functional change intended.
The second patch is the actual change.
Thanks,
Lars
[1] https://public-inbox.org/git/OF5D40FE06.C18CD7CD-ON002582B9.002B7A02-002582B9.002B7A07@notes.na.collabserv.com/
Base Ref: master
Web-Diff: https://github.com/larsxschneider/git/commit/0cbee9bd8d
Checkout: git fetch https://github.com/larsxschneider/git encoding-alias-v1 && git checkout 0cbee9bd8d
Lars Schneider (2):
convert: refactor conversion driver config parsing
convert: add alias support for 'working-tree-encoding' attributes
Documentation/gitattributes.txt | 19 ++++++
convert.c | 114 ++++++++++++++++++++++---------
t/t0028-working-tree-encoding.sh | 28 ++++++++
3 files changed, 129 insertions(+), 32 deletions(-)
base-commit: e3331758f12da22f4103eec7efe1b5304a9be5e9
--
2.18.0
next reply other threads:[~2018-07-08 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 18:30 larsxschneider [this message]
2018-07-08 18:30 ` [PATCH v1 1/2] convert: refactor conversion driver config parsing larsxschneider
2018-07-08 18:35 ` Lars Schneider
2018-07-09 20:01 ` Junio C Hamano
2018-07-10 16:25 ` Junio C Hamano
2018-07-08 18:30 ` [PATCH v1 2/2] convert: add alias support for 'working-tree-encoding' attributes larsxschneider
2018-07-08 18:39 ` Lars Schneider
2018-07-10 16:31 ` 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=20180708183036.29459-1-larsxschneider@gmail.com \
--to=larsxschneider@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jehan@orb.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
--cc=whee@smaertness.net \
/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).