forked from andreberg/gitx
-
Notifications
You must be signed in to change notification settings - Fork 79
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: brotherbard/gitx
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: experimental
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: kjg/gitx
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: fsevents
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 6 commits
- 12 files changed
- 3 contributors
Commits on Nov 19, 2010
-
Add PBGitRepositoryWatcher with FSEvents
This adds the PBGitRepositoryWatcher class, which monitors the working directory and the .git directory of the repository. If changes in any of those happen, a notification is sent to the default NSNotificationCenter. Reviewed-by: Johannes Gilger <heipei@hackvalue.de> Reviewed-by: Pieter de Bie <frimmirf+gitx@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for c11474f - Browse repository at this point
Copy the full SHA c11474fView commit details -
PBGitRepository: Init PBGitRepositoryWatcher
This allocs and inits a PBGitRepositoryWatcher when opening a PBGitRepository. Reviewed-by: Johannes Gilger <heipei@hackvalue.de>
Configuration menu - View commit details
-
Copy full SHA for 0768b55 - Browse repository at this point
Copy the full SHA 0768b55View commit details -
PBGitHistoryController: Use PBGitRepoWatcher
This sets up listeners in the commit/history controllers for NSNotifications sent by the PBGitRepositoryWatcher. It also implements how to act on these messages in separate methods, depending on the type of notification. Reviewed-by: Johannes Gilger <heipei@hackvalue.de>
Configuration menu - View commit details
-
Copy full SHA for 592b1f5 - Browse repository at this point
Copy the full SHA 592b1f5View commit details -
PBGitCommitController: Use PBGitRepoWatcher
This sets up listeners in the commit/history controllers for NSNotifications sent by the PBGitRepositoryWatcher. It also implements how to act on these messages in separate methods, depending on the type of notification. Reviewed-by: Johannes Gilger <heipei@hackvalue.de>
Configuration menu - View commit details
-
Copy full SHA for a1b7272 - Browse repository at this point
Copy the full SHA a1b7272View commit details -
PBGitRepoWatcher: Add preference and use it
This adds a preference (and description) for enabling/disabling the PBGitRepositoryWatcher. When opening a repository this preference is checked and the watcher isn't started if it's unset. Signed-off-by: Johannes Gilger <heipei@hackvalue.de>
Configuration menu - View commit details
-
Copy full SHA for fac02a9 - Browse repository at this point
Copy the full SHA fac02a9View commit details -
Configuration menu - View commit details
-
Copy full SHA for fb391c5 - Browse repository at this point
Copy the full SHA fb391c5View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff experimental...fsevents