annoyingly rounding off
Mark Smith
typo3org at awayand.sleepmail.com
Tue Jan 29 17:58:55 EST 2013
> Generally, any commit can be backported if it
> - fixes a bug (new features shouldn't be backported)
> - is fairly trivial to do so
> - doesn't introduce new or changed translatable strings
>
> I believe your commit fits all of the above criteria, so feel free to
> actually backport it. You can do this by
> - checking out the 2.4 branch and applying the same changes there
> (pretty easy with git cherry-pick).
> - Then change the commit message (eg. with git commit --amend)
> * it should start with [orig-rev] (in your particular example:
> [22673]).
> * remove the line holding BP (if it exists)
> * remove the line referring to the original svn commit (only there
> when working in a git repo)
> - Push the commit
Mike, would you be able to do this for me? I am a little bit overwhelmed
by this, as I am no developer...
More information about the gnucash-user
mailing list