Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

typo fix #36

Closed
wants to merge 1 commit into from
Closed

typo fix #36

wants to merge 1 commit into from

Conversation

dsteinbrunner
Copy link
Contributor

No description provided.

@ribasushi
Copy link
Collaborator

@ilmari Please no merge-comits unless chainsaw-approved, especially for such trivial changes. Fixed master force-pushed.

Cheers

@ilmari
Copy link
Contributor

ilmari commented Sep 16, 2013

@ribasushi Sorry, I did it so I could close the pull request via a the commit message, since I don't have permissions to do it via the web interface and didn't know if github was clever enough to auto-close on a fast-forward, non-rebased merge.

@ribasushi
Copy link
Collaborator

@ilmari Ironically the entire reason I opted to not share dbsrgits orga bits with many people was to avoid this very situation - merges are bad mkay? :) In any case you could not have known because ultimately I do not have these things documented anywhere. Work slowly progresses on that front...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants