Bram is reviewing patches and applying them upstream. The last patch state can always be found at the mercurial repository at code.google.com
When does a new release happen?
However code.google.com is lacking some social features which is why we want to provide official bitbucket and github mirrors
issues @ vim @ code.google.com I don't think there is a need to change that
Thus if you want to help and don't know what to do pick an item and solve it :)
Sent the patch or a pull request link to the vim-dev mailinglist.
Yes, this should be documented in the repo (TODO)
:set sts=4 sw=4 ts=8
However its not consistent
Adding .patch to a pull request yields the diff file
Currently two exist:
TODO: Which one should we prefer making pull requests against for what reasons?
It does not exist yet ? (TODO)
Because both features which are of interest to the community such as being able to submit "pull requests", comment on individual lines of commits etc.
Not supported (yet). I don't know about existing solutions. Eventually "hg-git" extension or such could be tried.
Both provide advanced features. Marc Weber slightly prefers git because it has the "remotes" feature. Example:
git remote add other-developer git-url git fetch other-developer # list all branches, the branches from other-developer will be prefixed by the # remote name "other-developer" git branch -a
PatchBranchExtension (hg) and topgit (git) both allow to keep hacking on multiple branches which may depend on each other and keeping them up to date. Finally you can export one patch easily
Marc Weber has written a top git introduction. The PatchBranchExtension is documented at the link above very well.
Of course for mercurial there is the well known mq extension, too. mq allows to reorder patches from a stack of patches and apply/unapply them easily. topgit and PatchBranchExtension are good at managing topic branches which depend on each other.
Do whatever works for you