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

[Steinar Bang <sb@dod.no>]

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

> I should have missed something in my explanation, the paranoid part is
> optional,

Right! :-)

> I mostly do the pull directly in master:

> - pull master to be up-to-date against origin
> - pull the remote tag in master
> - if I do not like, juste “git reset --hard to HEAD~”

Which is simple and straightforward.

(On a side note I've found it useful to add actual copy/pastable
commands with all such instructions. That increases the likelyhood of
people actually following the instructions (I know the actual
instructions are two messages earlier in the thread, but people will not
necessarily go there, or if they do, spend time figuring out which of
those commands are the ones you list above). Git has so many
possibilities, it is best learnt "by absorption"... or at least: use it
a lot, then read the "Pro git" book)

My personal preference is to just leave the other remote hanging
around.  It does no harm, and I can study the branches there if I should
feel the urge.

I also prefer to work with branches, and almost(*) exclusively using
merge.

(*) I rebase/cherry-pick when taking changes back to old branches, and
    when I've messed up a "fake merge", and git insists that it won't
    merge because the target branch is alreayd up to date...