-
Notifications
You must be signed in to change notification settings - Fork 202
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
Use version 2 of ext-idle-notify-v1 protocol #590
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [jinja2](https://github.com/pallets/jinja) from 3.1.4 to 3.1.5. - [Release notes](https://github.com/pallets/jinja/releases) - [Changelog](https://github.com/pallets/jinja/blob/main/CHANGES.rst) - [Commits](pallets/jinja@3.1.4...3.1.5) --- updated-dependencies: - dependency-name: jinja2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
This version allows for idle notifications to ignore idle inhibitors.
jjramsey
force-pushed
the
ext-idle-notify-update
branch
2 times, most recently
from
January 14, 2025 12:32
a827bae
to
9096354
Compare
I suggest using feature branches instead of the git checkout main
git checkout -b feature/notify-v1
[do changes and commit]
# maybe replace origin with the name of your remote
git push origin feature/notify-1:feature/notify-v1 Then when you want to sync changes from main: git checkout main
git pull
git checkout feature/notify-v1
git rebase main
# maybe replace origin with the name of your remote
git push --force origin feature/notify-1:feature/notify-v1 |
I did use a branch! It's just that I thought I knew more about rebasing than I did, and it got me in trouble. Anyway. for the record, the redone pull request is here: #596 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For now, this is only a draft, meant as a proof-of-concept client implementation of a revision to the ext-idle-notify protocol described in this merge request to wayland-protocols here: wayland/wayland-protocols!367.If implemented, it should allow Workrave to work on Wayland without interference from idle inhibitors.I mangled the rebase for my fork, so I'm going to nuke my branch and start over.