From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Philip Oakley <philipoakley@iee.email>,
Philip Oakley via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 4/4] doc add: renormalize is not idempotent for CRCRLF
Date: Sat, 6 Aug 2022 21:22:25 +0200 [thread overview]
Message-ID: <20220806192225.gu7o2avekbtcg6py@tb-raspi4> (raw)
In-Reply-To: <xmqq5yj6z5rx.fsf@gitster.g>
On Fri, Aug 05, 2022 at 03:26:10PM -0700, Junio C Hamano wrote:
> Philip Oakley <philipoakley@iee.email> writes:
>
> >> How about this:
> >>
> >> This option implies `-u`. Lone CR characters are untouched. CRCRLF cleans to CRLF.
> > That is probably sufficient. It drops the awkward 'idempotent'. And
> > indicates this edge case, though doesn't highlight that the resultant
> > CRLF still leaves the file only partially renormalised.
> >
> > I'll reword.
>
> It's been a few weeks since the last activity on this topic.
> Anything you guys need unblocked to move forward?
>
> Thanks.
>
Not from my point of view. My understanding is, that the short version is OK for
everybody:
This option implies `-u`. Lone CR characters are untouched. CRCRLF cleans to CRLF.
Is it OK to ask you for a local ammend to push this further ?
next prev parent reply other threads:[~2022-08-06 19:22 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 16:56 [PATCH 0/4] Add some Glossary terms, and extra renormalize information Philip Oakley via GitGitGadget
2022-07-09 16:56 ` [PATCH 1/4] glossary: add Object DataBase (ODB) abbreviation Philip Oakley via GitGitGadget
2022-07-09 16:56 ` [PATCH 2/4] glossary: add commit graph description Philip Oakley via GitGitGadget
2022-07-09 21:20 ` Junio C Hamano
2022-07-10 21:37 ` Philip Oakley
2022-08-30 14:33 ` Philip Oakley
2022-07-09 16:56 ` [PATCH 3/4] glossary: add reachability bitmap description Philip Oakley via GitGitGadget
2022-07-09 16:56 ` [PATCH 4/4] doc add: renormalize is not idempotent for CRCRLF Philip Oakley via GitGitGadget
2022-07-09 21:06 ` Junio C Hamano
2022-07-10 21:52 ` Philip Oakley
2022-07-10 22:04 ` Junio C Hamano
2022-07-10 22:25 ` Philip Oakley
2022-07-10 7:48 ` Torsten Bögershausen
2022-07-10 22:09 ` Philip Oakley
2022-08-05 22:26 ` Junio C Hamano
2022-08-06 19:22 ` Torsten Bögershausen [this message]
2022-08-08 14:32 ` Philip Oakley
2022-08-08 16:21 ` Junio C Hamano
2022-08-09 18:44 ` Torsten Bögershausen
2022-08-10 14:44 ` [PATCH v2 0/1] .. Add extra renormalize information Philip Oakley
2022-08-10 14:44 ` [PATCH v2 1/1] doc add: renormalize is not idempotent for CRCRLF Philip Oakley
2022-08-10 17:11 ` Torsten Bögershausen
2022-08-10 17:42 ` Junio C Hamano
2022-07-09 21:34 ` [PATCH 0/4] Add some Glossary terms, and extra renormalize information Junio C Hamano
2022-07-10 15:20 ` Philip Oakley
2022-10-22 22:25 ` [PATCH v2 0/3] Add some Glossary of terms information Philip Oakley
2022-10-22 22:25 ` [PATCH v2 1/3] doc: use 'object database' not ODB or abbreviation Philip Oakley
2022-10-22 22:25 ` [PATCH v2 2/3] glossary: add "commit graph" description Philip Oakley
2022-10-25 12:31 ` Derrick Stolee
2022-10-29 16:32 ` Philip Oakley
2022-10-22 22:25 ` [PATCH v2 3/3] glossary: add reachability bitmap description Philip Oakley
2022-10-24 7:43 ` Abhradeep Chakraborty
2022-10-24 16:39 ` Junio C Hamano
2022-10-24 21:23 ` Philip Oakley
2022-10-25 12:34 ` Derrick Stolee
2022-10-25 15:53 ` Junio C Hamano
2022-10-29 16:36 ` Philip Oakley
2022-10-23 1:49 ` [PATCH v2 0/3] Add some Glossary of terms information Junio C Hamano
2022-10-29 16:41 ` [PATCH v3 0/4] " Philip Oakley
2022-10-29 16:41 ` [PATCH v3 1/4] doc: use 'object database' not ODB or abbreviation Philip Oakley
2022-10-29 16:41 ` [PATCH v3 2/4] glossary: add "commit graph" description Philip Oakley
2022-10-29 16:41 ` [PATCH v3 3/4] glossary: add reachability bitmap description Philip Oakley
2022-10-29 16:41 ` [PATCH v3 4/4] doc: use "commit-graph" hyphenation consistently Philip Oakley
2022-10-29 17:24 ` [PATCH v3 0/4] Add some Glossary of terms information Taylor Blau
2022-10-29 17:34 ` Philip Oakley
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=20220806192225.gu7o2avekbtcg6py@tb-raspi4 \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=philipoakley@iee.email \
/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.