Hi Ferry,
I suppose this would be something for the contrib/ section. I wouldn't
be all together opposed to filling this directory with lots of
different integrations for various project management applications,
web servers, and so forth, but one pitfall I've seen numerous times in
my projects
I'm curious whether there is a merge policy in place for those *for-jason
branches. Will they be fast forward only or reasonable they may be reset
since it's really just a contract for you and the person providing the
series, rather than something others should be following.
For example. In
Hi guys,
I have this Trac component that integrates CGit into Trac, see
https://github.com/reposerf/tracCGit
AFAIK its biggest user is Fedora, and I use it too at a clients site
(it's mainly for them that I wrote it).
Would you consider it worth integrating it in the cgit repo or hosting
Hey folks,
I wanted to update you on a conversation a few of us have been having
off-list. In order to hasten the speed of development, we're making
some changes to the way things are done.
All submitted patch series will now live in feature branches. Each
feature branch will be owned by either
