Re: Beginning to use async.el to help Gnus' interactivity

[Steinar Bang <sb@dod.no>]

>>>>> Ted Zlatanov <tzz@lifelogs.com>:

> Contact me off-list for write access.  Same for anyone who believes they
> need it.  I'd prefer more developers to more patches :)

One possibility would be to create a git branch, push it to a repo on
github, and then Ted can add that repo as a remote, fetch the branch
from that remote, and then merge and push.

It's less work than it sounds like.

For the branch pusher, it should be something like:
 1. if you've made the fixes against master, create a git branch for the
    fixes:
     git checkout jw-async-changes
 2. create a git repo on github (or your own git server or whatever),
    called for the purposes of these examples jw-gnus (this is the bit
    that takes most work, if you don't already have a github account or
    your own git server or a git account on a different provider)
 3. add that repo as a remote to the local gnus repo
     cd ~/git/gnus/
     git remote add jw-gnus https://github.com/jw/jw-gnus.git
 4. assuming you're already on the branch with the fixes push it to the
    new git repo:
     git push jw-gnus HEAD

Pulling and merging and pushing would then be:
 1. Add the new remote, and fetch its branches:
     git remote add jw-gnus https://github.com/jw/jw-gnus.git
     git fetch jw-gnus
 2. Merge the branch fetched from jw-gnus
     git merge jw-gnus/jw-async-changes
 3. Push the merge results:
     git push origin HEAD

The result will have the full git history of the changes, with original
committer (unlike a patch).