[Flow] Documentation patches and backports

[Franz Kugelmann]

Hi list,

just talked with Christian Müller, thanks Christian for the info!
Answers see below.

> Hi list, especially core team,
>
> lately i pushed some small documentation patches and aim to keep going
> with it, hopefully someday also adding more than just tiny fixes.
>
> To keep this as smooth as possible and as little work for others as
> possible here some questions coming up for me:
>
> 1. Is it better to commit lots of tiny patches with sometimes just a
> spelling correction or would it be better to collect some of them (if
> more found) into one patch?
> So far i find smaller patches better because the review is so easy then,
> but i am open for suggestions :)

i will keep to the small patches.


>
> 2. Bastian added the release information to the commit messages for some
> of the patches. Thanks! From now on i try to do this myself right from
> the beginning.
> If a patch is verified and merged for master, should i backport it for
> 2.0, following the procedure given in [1] and thus create a new patchset
> which has again to be verified and merged?

suggestion was correct, i will bring in the backport patches as well as 
described in [1].

>
>
> In my opinion the existing documentation is already a great and vast
> resource of information, very well done guys, keep rocking!
>
> Kind regards
> Franz
>
> [1]
> http://wiki.typo3.org/Contribution_Walkthrough_with_CommandLine#Backporting_a_change_to_other_branches
>
>


-- 
--------------------------------------
franz.kugelmann at elementare-teilchen.de