Re: [PATCH] Use `gnus-parameters' in `gnus-group-split-fancy'

[Steinar Bang <sb@dod.no>]

>>>>> Daniel Dehennin <daniel.dehennin@baby-gnu.org>:

> The following changes since commit b4bc300f0dcddc2b17bb50a3501ed6e6db1ef12c:

>   Update copyright year to 2014 (2014-01-01 10:39:44 +0000)

> are available in the git repository at:

>   git://git.baby-gnu.net/gnus.git tags/feature/use-gnus-parameters-in-gnus-group-split-fancy

HOWTO for adding these to gnus master:
 - Enter your git gnus clone
    cd ~/git/gnus
 - Add and fetch the baby-gnu gnus repo
    git remote add baby-gnu git://git.baby-gnu.net/gnus.git
    git fetch --tags baby-gnu
    git fetch baby-gnu
 - Update the gnus master branch to HEAD
    git checkout master
    git pull
 - Merge in the tag, and stop for inspection (magit is nice for looking
   at the merge results after this step, and also for fixing merge
   conflicts): 
    git merge --no-ff --no-commit feature/use-gnus-parameters-in-gnus-group-split-fancy
 - After inspection and fix, either `c' to commit from inside magit, or
   commit on the command line:
    git commit

The difference to doing this as opposed to applying the patch, is that
you could potentially get the full history of the change with multiple
commits (in this case this was just a single commit).

If one decide to revert the commit, just do a:
 git checkout master
 git reset --hard origin/master
(the extra checkout is to be doubly sure I am on the right branch before
doing the hard reset)

(For those that hasn't used git yet: the reason this works is git's
storage-by-content approach, that means that a commit with the same
changes and the same metadata is seen as the same commit no matter where
it comes from. Ie. a merge with the master on baby-gnu into master from
gnus.org will only see a difference for commits that have been added on
baby-gnu)