Wilfred,   
      
   13 Jan 13 17:32, you wrote to me:   
      
    RC>> at least for the debian packaging...   
      
    WV> But why create a separate branch for it?   
      
      Main reason is that the Debian packaging is separately versioned; even for    
   a generic debian branch, but especially for packaging targeted to specific    
   distro version.  For instance; the branch 'lucid' was originally branched off    
   of the debian branch and at that time consisted of the v3.3.0 MakeNL code and    
   the v3.3.0-1 Debian packaging. The build daemons on launchpad.net require that    
   the uploads target a particular ubuntu distribution; I wanted this new one (to    
   the ftnapps project) to target v10.04 LTS (lucid) in order to replace an old    
   package version already there; so I updated debian/changelog for that    
   (4af32d0), created a new source package from that change and uploaded it.     
   (i386 & amd64 builds for it were successful...) I don't plan to do much else    
   with the lucid branch except needed and/or requested changes or fixes. I    
   haven't created a branch for Ubuntu v12.04 LTS (precise) yet but I will being    
   doing so after I finish some updates to the packaging.   
      
      
    WV>  I supose the debian specific files are in their own subdirectory, so   
    WV> there is no problem when they live in the master branch.   
      
      Actually, there can be; although not as much as there was with the old    
   package format.   
      
      
    WV>  And now you have to do a merge from master   
    WV> to the debian branch, everytime you want to do a release...   
      
      Yes, a release of MakeNL. Not a release of a debian package for MakeNL,    
   which is separately tracked and might be for a generic debian package (the    
   'debian' branch) or for Ubuntu v10.04 on the branch 'lucid', or ...   
      
      
      
      
      
      
   Jame   
      
   --- GoldED+/LNX 1.1.5--b20111217   
    * Origin: RJC eeePC (1:120/419)