summaryrefslogtreecommitdiff
path: root/_posts/2009-10-05-dealing-with-lineendings.textile
diff options
context:
space:
mode:
authorCameron McEfee <cameron@github.com>2011-05-27 14:01:53 -0700
committerCameron McEfee <cameron@github.com>2011-05-27 14:01:53 -0700
commit1771997794464b56d0e58317260093e98aabda1b (patch)
tree10040909d8d7ca618983e017815c7b990438c7a5 /_posts/2009-10-05-dealing-with-lineendings.textile
parent4e9c4c8ca65dd32a4616cc3711f8d24927341139 (diff)
add new categories
Diffstat (limited to '_posts/2009-10-05-dealing-with-lineendings.textile')
-rw-r--r--_posts/2009-10-05-dealing-with-lineendings.textile2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2009-10-05-dealing-with-lineendings.textile b/_posts/2009-10-05-dealing-with-lineendings.textile
index 3296e3d..77f0572 100644
--- a/_posts/2009-10-05-dealing-with-lineendings.textile
+++ b/_posts/2009-10-05-dealing-with-lineendings.textile
@@ -2,7 +2,7 @@
layout: default
title: Dealing with line endings
description: How to ensure that line endings are consistent in your repo
-categories: troubleshooting windows mac linux
+categories: troubleshooting
---
<p class="intro">Line endings... the scourge of every Windows-based developer that tries to mingle with linux- or mac-based developers. Though most modern text editors can handle both newline types without issue, git is not as graceful.</p>