git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Cross-Platform Version Control (was: Eric Sink's blog - notes on git, dscms and a "whole product" approach)

From
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date
Apr 28, 2009, 21:00 UTC
Message-ID
<200904282300.57087.robin.rosenberg.lists@dewire.com>
In-Reply-To
<m3r5zdnhqu.fsf@localhost.localdomain>
tisdag 28 april 2009 13:24:31 skrev Jakub Narebski <jnareb@gmail.com>:
Show 6 quoted lines
> Line endings (issue 8.) is in theory and in practice (at least for
> Git) a non-issue.  
> 
> In theory you should use project's convention for end of line
> character in text files, and use smart editor that can deal (or can be
> configured to deal) with this issue correctly.
Windows people will disagree.
> In practice this is a matter of correctly setting up core.autocrlf
> (and in more complicated cases, where more complicated means for git
> very very rare, configuring which files are text and which are not).

Which proves it is an issue or we wouldn't need to tune settings to make it work right. A non-issue is something that "just works" without turning knobs. I had had to think more than once on what the issue was and the right way to solve these issues. It can be considered wierd, because Eclipse on Linux generated files with CRLF which I happily committed and Git on Windows happily converted to LF and determined that the HEAD and index was out of sync, but refuesed to commit the CRLF>LF change becuase there was no "diff".. You know the fix, but don't tell me it's not an issue.

-- robin
Previous: Jakub NarebskiNext: Martin Langhoff
Message 3 of 39 in “Eric Sink's blog - notes on git, dscms and a "whole product" approach”
  1. Martin LanghoffApr 27, 2009
  2. Cross-Platform Version Control (was: Eric Sink's blog - notes on git, dscms and a "whole product" approach)Jakub Narebski, Apr 28, 2009
  3. Robin RosenbergApr 28, 2009
  4. Martin LanghoffApr 29, 2009
  5. Jeff KingApr 29, 2009
  6. Markus HeidelbergApr 29, 2009
  7. Jakub NarebskiApr 29, 2009
  8. Martin LanghoffApr 29, 2009
  9. Jakub NarebskiApr 28, 2009
  10. Sitaram ChamartyApr 29, 2009
  11. Why Git is so fast (was: Re: Eric Sink's blog - notes on git, dscms and a "whole product" approach)Jakub Narebski, Apr 30, 2009
  12. Michael WittenApr 30, 2009
  13. Jakub NarebskiApr 30, 2009
  14. Shawn O. PearceApr 30, 2009
  15. Kjetil BarvikApr 30, 2009
  16. Shawn O. PearceApr 30, 2009
  17. Kjetil BarvikApr 30, 2009
  18. Steven NoonanMay 1, 2009
  19. James PickensMay 1, 2009
  20. Kjetil BarvikMay 1, 2009
  21. Mike HommeyMay 1, 2009
  22. Kjetil BarvikMay 1, 2009
  23. Tony FinchMay 1, 2009
  24. Dmitry PotapovMay 1, 2009
  25. Mike HommeyMay 1, 2009
  26. Dmitry PotapovMay 1, 2009
  27. Shawn O. PearceApr 30, 2009
  28. Jeff KingApr 30, 2009
  29. Linus TorvaldsMay 1, 2009
  30. Jeff KingMay 1, 2009
  31. david@lang.hmMay 1, 2009
  32. Nicolas PitreMay 1, 2009
  33. Daniel BarkalowMay 1, 2009
  34. Linus TorvaldsMay 1, 2009
  35. david@lang.hmMay 1, 2009
  36. Nicolas PitreApr 30, 2009
  37. Alex RiesenApr 30, 2009
  38. Andreas EricssonMay 4, 2009
  39. Jakub NarebskiApr 30, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.