[Gnumed-devel] Git and where to find production GNUmed source pending the next bug-fix release

[Jim Busser]

Q1 - is each commit in Git labelled in the vcs as a "patch" and are such 
patches all "applied" as part of the commit?

Q2 - I understand that in Gitorious (apart from clones) Karsten is maintaining 
always at least two branches

        1) "master" --> bleeding edge code for both development and bug-patching
                (maybe not labelled bug-patching when it's in master?)

        2) at least one production release branch, for bug-patching, currently 
0.8 branch

        http://gitorious.org/gnumed/gnumed/commits/rel-0-8-patches

… and this makes it possible that some time can elapse between a branch 
receiving bug-fixes and when the next (bug-fix production release) gets

        tagged
        packaged

… all correct?


Q3 - during this interval, clicking the "Source tree" listing button will show 
(along the right margin)

                        Branches:

                                master
                                ooo
                                rel-0-1-patches
                                …
                                rel-0-8-patches

                        Tags

                                TEST_STRUTS_0_02
                                client
                                …
                                rel-0-1
                                …
                                rel-0-8-6
                                …

and so if the vcs would get updated with fixes that get committed into branch

                                rel-0-8-patches

then it should be possible (before 0.8.7 is tagged / released) to download

                                rel-0-8-patches

as tar.gz and run (from vcs) code that already contains the bug fix patch?

-- Jim