git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Jonathan Nieder'" <jrnieder@gmail.com>,
	"'Torsten Bögershausen'" <tboegi@web.de>
Cc: "'Robert Dailey'" <rcdailey.lists@gmail.com>,
	"'Git'" <git@vger.kernel.org>
Subject: RE: Automatic core.autocrlf?
Date: Fri, 31 Aug 2018 07:57:04 -0400	[thread overview]
Message-ID: <000c01d44121$bf563090$3e0291b0$@nexbridge.com> (raw)
In-Reply-To: <20180831032917.GC98946@aiede.svl.corp.google.com>


On August 30, 2018 11:29 PM, Jonathan Nieder wrote:
> Torsten Bögershausen wrote:
> 
> > My original plan was to try to "make obsolete"/retire and phase out
> > core.autocrlf completely.
> > However, since e.g. egit/jgit uses it
> > (they don't have support for .gitattributes at all) I am not sure if
> > this is a good idea either.
> 
> Interesting.  [1] appears to have intended to add this feature.
> Do you remember when it is that you tested?
> 
> Feel free to file bugs using [2] for any missing features.
> 
> [1] https://git.eclipse.org/r/c/60635
> [2] https://www.eclipse.org/jgit/support/

My testing was done on EGit 5.0.1 yesterday, which does not provide a default to core.autocrlf.

Cheers,
Randall


  reply	other threads:[~2018-08-31 11:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27 14:10 Automatic core.autocrlf? Robert Dailey
2018-08-27 15:35 ` Torsten Bögershausen
2018-08-27 15:52   ` Duy Nguyen
2018-08-27 17:29     ` Robert Dailey
2018-08-27 17:32     ` Andrei Rybak
2018-08-27 18:22       ` Andrei Rybak
2018-08-28  0:14       ` brian m. carlson
2018-08-30 14:53       ` Robert Dailey
2018-08-30  4:54 ` Jonathan Nieder
2018-08-30 14:57   ` Robert Dailey
2018-08-30 18:56     ` Torsten Bögershausen
2018-08-30 19:10       ` Randall S. Becker
2018-08-31  3:29       ` Jonathan Nieder
2018-08-31 11:57         ` Randall S. Becker [this message]
2018-08-31 13:17           ` Torsten Bögershausen

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000c01d44121$bf563090$3e0291b0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=rcdailey.lists@gmail.com \
    --cc=tboegi@web.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).