Hi all, [ about committing to B_Release ]
> Depending on the exact needs, it might take some advanced git-fu, and > the simplest solution may turn out to be to just copy the latest state > and commit that to B_Release, without merging the specific file-history > on the branch. And that's exactly how we're supposed to do it, even in the CVS days: Once a document reaches a publishable state (again), you copy it to B_Release, overwriting the current content (which represents the previous publishable state of that document). This way, B_Release's head always contains the most recent buildable and publishable version of every manual. Cheers, Paul ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
