I've once again thought up a different common structure for website pages, I hope this one sticks longer than the ones before, but this limits duplication of data somewhat and keeps maintenance costs of these pages fairly low.
2.2 KiB
git-auto-commit-mode
<script src="/keyjs.js" type="text/javascript"></script> <script type="text/javascript"> keyjs_initialize({ "u": [ "keyjs_goto", "../index.html" ], "h": [ "keyjs_goto", "http://ryuslash.org" ] }); </script>
What does it do?
git-auto-commit-mode
is a minor mode for GNU Emacs that, when
enabled, tries to commit changes to a file after every save. It can
also try to push to the default upstream.
Why was it written?
Some projects / files don't need a very fancy commit log or anything and are typically only modified in small ways. Configuration files are a good example, where most changes are just single lines added, removed or changed. In these projects it can save some effort to just automatically commit them after every change.
Who is it for?
Anyone who makes a lot of small, separate, changes to a bunch if
git-tracked files and is tired of always having to go through the
git add; git commit -m description
process.
Data
Version | 0 (development only) |
Language | Emacs Lisp |
License | GPLv3 |
Features
-
Automatically commit changes to a file after each save.
- The commit message will contain the file name relative to the repository root.
- Optionally, automatically push commits to the default upstream.
More…
For further instructinos I would refer you to the README and /ryuslash/orgweb/src/commit/8cf9315c3c4ffd41f476fe44af1551bcb909a421/site/projects/manual.