Fwd: [moonbase-core] Florin's updates (#25)

[jean.bruenn at ip-minds.de]

Hello Auke,

I guess this requirement has to do with reverts later on (making them
easier)? Is there _any_ other way, to do this? I know that a few
developers have no problem working with branches, and even if everyone
says one gets used to it, I find it pretty confusing and it adds a
lot of extra work imo.

It might be also useful if someone would write down (I got a list
from ratler) the exact workflow. Currently, (iirc) I have to switch 
into
the specific repository (1 of 11) then I have to issue some git
commands to update using upstream, then I have to create a branch,
then I have to make my changes, then I have to push it, then I
have to visit the website to make a pull request, then I have to
keep this branch till my pull request got accepted.. One day I'll
end up with 10 branches in 11 repositories .. just thinking about
that makes my head hurt..

once again. Anything easier apart from not committing anymore at all? 
:)

Jean

On Mon, 23 Jul 2012 20:07:21 -0700, Auke Kok wrote:
> All,
>
> I'm going to REJECT any pull request for moonbase-core that combines
> unrelated changes in one of multiple commits.
>
> If you want changes to moonbase-core to be accepted, you *NEED* to
> make these changes on *SEPARATE* branches and make *SEPARATE* git 
> pull
> requests.