From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Luca Boccassi <bluca@debian.org>
Cc: Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
dev@dpdk.org, John Alexander <John.Alexander@datapath.co.uk>
Subject: Re: [dpdk-dev] [kmods PATCH] windows: normalize line-endings
Date: Wed, 11 Nov 2020 18:11:17 +0300 [thread overview]
Message-ID: <20201111181117.112e3f43@sovereign> (raw)
In-Reply-To: <e706aa32aade7232f697795d8177e186ac1b7607.camel@debian.org>
On Tue, 03 Nov 2020 10:05:43 +0000, Luca Boccassi wrote:
> The patch looks good to me, as I really need all files to be checked in
> with LF only as a hard requirement before I can upload to
> Debian/Ubuntu, so:
>
> Acked-by: Luca Boccassi <bluca@debian.org>
>
> Does the change also stop future check-ins of CRLF files?
Yes. Regardless of core.autocrlf setting on Windows machine, where
files with CRLF are created, they're checked-in with LF and checked-out with
LF on Linux. Sorry for the late reply.
next prev parent reply other threads:[~2020-11-11 15:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 22:55 [dpdk-dev] [kmods PATCH] windows: normalize line-endings Dmitry Kozlyuk
2020-11-03 4:05 ` Narcisa Ana Maria Vasile
2020-11-03 7:42 ` Dmitry Kozlyuk
2020-11-03 10:05 ` Luca Boccassi
2020-11-11 15:02 ` Luca Boccassi
2020-11-11 15:11 ` Dmitry Kozlyuk [this message]
2020-11-03 20:49 ` Narcisa Ana Maria Vasile
2020-11-11 15:02 ` Thomas Monjalon
2020-11-11 15:03 ` Luca Boccassi
2020-11-11 15:09 ` Luca Boccassi
2020-11-12 20:16 ` Luca Boccassi
2020-11-12 20:15 ` [dpdk-dev] [kmods PATCH v2] " luca.boccassi
2020-11-12 23:17 ` Thomas Monjalon
2020-11-13 7:06 ` Dmitry Kozlyuk
2020-11-13 9:43 ` Thomas Monjalon
2020-11-13 9:52 ` Luca Boccassi
2020-11-13 9:50 ` [dpdk-dev] [kmods PATCH v3 1/2] windows: remove .gitattributes luca.boccassi
2020-11-13 9:50 ` [dpdk-dev] [kmods PATCH v3 2/2] windows: normalize line-endings luca.boccassi
2020-11-13 15:12 ` Thomas Monjalon
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=20201111181117.112e3f43@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=John.Alexander@datapath.co.uk \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=navasile@linux.microsoft.com \
/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.