https://github.com/benjamn/patches
My mozilla-central patch queue
https://github.com/benjamn/patches
Last synced: 6 months ago
JSON representation
My mozilla-central patch queue
- Host: GitHub
- URL: https://github.com/benjamn/patches
- Owner: benjamn
- Created: 2008-12-22T00:56:39.000Z (over 17 years ago)
- Default Branch: master
- Last Pushed: 2010-06-25T17:02:03.000Z (about 16 years ago)
- Last Synced: 2025-02-05T16:16:39.142Z (over 1 year ago)
- Homepage:
- Size: 1.06 MB
- Stars: 3
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.markdown
Awesome Lists containing this project
README
# RATIONALE
Why on earth would I use git to manage a mercurial patch queue? Not because git is more efficient than mercurial; any advantage would be unappreciable for so few files. Nor because I am particularly more comfortable with git than mercurial; I am not. No, the real reason I'm using git in preference to mercurial is that I want to host my patch queue remotely, publicly, and github is simply the best free hosting solution for revision-controlled code.
This decision has the side effect of making my day-to-day work at Mozilla completely transparent. For some time now I've been wondering how best to take advantage of this incredible luxury, and I think I've found my way.
Watch my progress if you're interested, or if you just want to give my work ethic a boost. Having an audience is tremendously encouraging.
## Some other benefits I've noticed:
- Not having the ".hg" directory in my patches directory means I can issue mercurial commands from inside the patches directory.
- Mercurial behaves nicely when no "status" file exists, so I've chosen not to commit that file.