deac
/
gitolite
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updated Welcome to the gitolite wiki!! (markdown)

master
sitaramc 2012-01-04 01:48:45 -08:00
parent 7456937555
commit e7bc7bd4a6
1 changed files with 20 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
Home.md

@ -6,6 +6,17 @@ Please start reading [here](http://sitaramc.github.com/gitolite/) to learn about
----
**Support**
* Please **don't** send me messages via github's "issues" system, linkedin comments/discussion, stackoverflow questions, google+ "streams", and any other Web 3.0 "coolness".
* Please **don't** send me pull requests via github. Instead, send me an email saying what URL and what branch to pull. (My reasons are at the bottom of this page).
The main support page for gitolite is [here](http://sitaramc.github.com/gitolite/support.html). Email addresses and contact info are [here](http://sitaramc.github.com/gitolite/index.html#contact_and_license_)
Support requests that indicate insufficient reading or understanding of the enormous amount of documentation that comes with gitolite will be answered only if time permits. This applies especially to **ssh issues**.
----
My gpg key (should be available at least from pgp.mit.edu keyserver, probably most others as well):
pub 4096R/088237A5 2011-10-25
@ -16,21 +27,6 @@ My gpg key (should be available at least from pgp.mit.edu keyserver, probably mo
----
**Support**
[This](http://sitaramc.github.com/gitolite/support.html) is the main support page.
The rest of this info is specific to github users, etc.
* Please **don't** send me messages via github's "issues" system, linkedin comments/discussion, stackoverflow questions, google+ "streams", and any other Web 3.0 "coolness".
* Please **don't** send me pull requests via github. Instead, send me an email saying what URL and what branch to pull.
Email addresses and contact info are [here](http://sitaramc.github.com/gitolite/index.html#contact_and_license_)
Support requests that indicate insufficient reading or understanding of the enormous amount of documentation that comes with gitolite will be answered only if time permits. This applies especially to **ssh issues**.
----
**Donations**
*Disclaimer: this is my personal opinion and does not necessarily reflect that of my employer. The disclaimer applies especially strongly to para 3 below*.
@ -39,4 +35,12 @@ I've had people ask me how they can donate to gitolite. The first part of the a
The second part of the answer is that if you feel the need to donate, please donate to either the [VIM project](http://www.vim.org/sponsor/index.php) or the [Perl Foundation](http://donate.perlfoundation.org/), both of which I consider indispensable to my work.
I have used open source for almost 17 years now, both personally and at work, and until now have never actually given back in any significant way other than evangelism. Thus the third part of the answer is that you can actually donate to *any* FOSS project (other than projects that use Mono) that you think makes a big difference in your life, and, I will consider myself thanked adequately :-)
I have used open source for almost 17 years now, both personally and at work, and until now have never actually given back in any significant way other than evangelism. Thus the third part of the answer is that you can actually donate to *any* FOSS project (other than projects that use Mono) that you think makes a big difference in your life, and, I will consider myself thanked adequately :-)
----
My reasons for not using the issues system and pull requests:
The issues system does have an email interface, but it is not a substitute for email. I can't cc anyone else when I want to, for instance (well I can, but any response the original requester then makes using the website will not get cc-d to the person I cc-d).
The pull system forces a --no-ff even if the merge is at the top of my branch and doesn't need one. It also gives me no chance to fix up minor typos, add any more text to the commit message, etc. (I can do that afterward, but this forces a "push -f" or a trivial "typofix" commit).