-
Notifications
You must be signed in to change notification settings - Fork 52
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
Get Started #1
Comments
Sounds good to me. I was thinking it could be a good idea to write unexported wrappers against the various OS X bits and then figure out the exported API from that. Just a thought. |
I made a pull request for some (minor) work I did earlier today #2. Mostly reading some of the FSEvents documentation. I switched the teams around so you have the commit bit on this repo now. |
Sadly your day is my night. It's like Ladyhawke. |
Lol. It's actually my afternoon, but the first chance to do any work today. On Sun, Nov 16, 2014 at 3:54 PM, Nathan Youngman [email protected]
|
Thanks Sam. Please take a look at Google's CLA too. |
Oh, and feel free to copy INTERNALS.md over here too. I felt like it should be under your name, since you wrote it. It probably will end up needing some revisions, at least the second half. |
Hi Nathan, Sorry for the delay getting back to you.
|
Thanks Peter. I moved this discussion to the fsnotify repository. This repo is specific to fsevents on OS X. Better Windows support would be great! Linux, I have no idea if/what there is for journalling. |
# This is the 1st commit message: update Travis CI config travis: update golint location travis: macOS 10.10 # The commit message #1 will be skipped: # travis
Refer here: howeyc/fsnotify#54
I believe that we can begin with the code I originally contributed to fsnotify, and modify it to suit.
The text was updated successfully, but these errors were encountered: