-
Notifications
You must be signed in to change notification settings - Fork 0
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
Ignore notes #2
Ignore notes #2
Conversation
* `group by` in aggregation * data hygiene * explain the `%%sqlite` magic
2. Put data hygiene in discussion of joins. 3. Got rid of 'next steps' sections.
First version of glossary.
…-orgs-badges Removing includes and images for instructors, orgs, and badges (which were almost never used).
…e unsized images as a result
Adding diagrams for novice lessons.
…en building on linux mint (ubuntu derivative). * ipython is too old -> install 1.1 via pip * some python packages are required -> install via apt-get
Comments on problems with building bc under linux
…edits Incorporating many of @wking's changes (but not all); still unsure what to say about `-u`
- use Git when talking about the command - fix typo - unix directory slashes - line lengths
Hi Pauline, Yeah, I guess I need a github course too :) I don't know if there is a way for other people to modify the code on a PR, On Mon, Dec 9, 2013 at 7:49 PM, Pauline Barmby notifications@github.comwrote:
|
If multiple users have write access to the repository that the PR branch originates from, they can update the branch and the PR will update automatically. |
added table and some MD formatting to 01-backup.md, deleted 05-undo.md
Hey Dave,
I made a few small changes - over to "vanilla" git status, and changing the name of the subdirectory to results/
instead of data/. Did not do anything about where the material gets included (as separate page or callout section) since there didn't seem to be consensus about this.
I would have changed the files in the PR directly but I didn't know how to do this (maybe it's not possible)? I will try to add you as a collaborator to my repo and then we can skip one merge step, I think.