Re: saving copies of the messages sent in Gnus

[Steinar Bang <sb@dod.no>]

>>>>> Steinar Bang <sb@dod.no>:

[snip!]
>  - one branch per patch (which is a bit of clutter, but keep different
>    patches in nice, isolated, side tracks.  The branches can be
>    deleted, when the patches they contained are merged into the master
>    branch)
[snip!]
> Though it may seem like creating a lot of clutter, to people unfamiliar
> with git, I would actually recommend the first approach: store each
> patch as a feature branch made from master, and push the branch to
> git.gnus.org. 

> Afterwards it is much easier to pick up the changes from the feature
> branch, than to collect a lot of patches floating around.  And the
> feature branches can be deleted after they have been merged into
> master.

It's also possible for people without gnus git repo write access, to:
 - make changes as local branches in the local repo
 - push their local repo to some publicly readable repo (eg. on github)

Then Lars, or whoever is integrating the patches, can:
 - add the publicly available repository as a remote
 - fetch from that repository
 - merge branches from that repository into git master

I have to admit that git is really quite clever...