Skip to content

Two readme's #759

Closed
blainesch opened this Issue Dec 20, 2012 · 0 comments

2 participants

@blainesch
Union of RAD member

We have two readme files. "README.md" and "readme.md".

This majorly foobars my lithium (Mac) saying I always have a dirty branch and that I edited a file, I cannot check it out since it's fine, and if I delete them both then I deleted them both.

Yikes this is annoying.

The real question, which one should I kill? The most recent one "readme.md" was updated a few weeks ago so I'll aim for the other.

@blainesch blainesch pushed a commit that referenced this issue Dec 20, 2012
Blaine Schmeisser Delete README.md and leave readme.md - Fixes #759 614f732
@nateabele nateabele closed this Dec 21, 2012
@leek leek added a commit that referenced this issue Apr 11, 2013
@leek leek Merge branch 'dev' of github.com:ServiceRunner/lithium into dev
* 'dev' of github.com:ServiceRunner/lithium:
  Doing a recursive unset of _id fields in the DB exporter, as MongoDB doesn't let you use $set and modify _id
  Revert "Modifying Collection and Entity so that you can pass in $options if you so desire. This allows you to"
  Modifying Collection and Entity so that you can pass in $options if you so desire. This allows you to for example pass in custom data handlers if desired for specific object handling when calling Entity->data()
  Revert "Modifying Collection and Entity so that you can pass in $options if you so desire. This allows you to"
  Modifying Collection and Entity so that you can pass in $options if you so desire. This allows you to for example pass in custom data handlers if desired for specific object handling when calling Entity->data()
  Revert "Modifying Collection and Entity so that you can pass in $options if you so desire. This allows you to"
  Modifying Collection and Entity so that you can pass in $options if you so desire. This allows you to for example pass in custom data handlers if desired for specific object handling when calling Entity->data()
  Making Unit return the value of the asserted Expresion consistently
  Revert "Modifying Collection and Entity so that you can pass in $options if you so desire. This allows you to"
  Making Unit return the value of the asserted Expresion consistently
  Fix bug with how results are rendered.
  Delete README.md and leave readme.md - Fixes #759
  Modifying Collection and Entity so that you can pass in $options if you so desire. This allows you to for example pass in custom data handlers if desired for specific object handling when calling Entity->data()
  Add documentation for the mocker class
7da1ae6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.