[fpc-pascal] GLPT v0.1.1 released

Graeme Geldenhuys mailinglists at geldenhuys.co.uk
Thu Oct 11 22:07:20 CEST 2018

On 11/10/18 05:39, Darius Blaszyk wrote:
> Not sure though if you need to stash your local changes first to prevent
> losing them.

For contribution to a project I ALWAYS recommend they work in a separate
branch. There are many benefits to that from both side (per writing code
and person merging changes upstream).

Some benefits:
  * They can do a pull from the upstream repository and it doesn't
affect there branch - no merge conflicts, no stashes required.
  * Developer can the review upstream changes as and when needed. When
they have the time, they can rebase or merge upstream changes into there
branch. At a convenient time.
  * Seeing what has changes between branches is supper simple - branches
are done correctly in Git, and makes work very easy.
  * Super simple one line command to generate a set of patches (similar
to previous point) and email those, in case the developer doesn't have a
publicly accessible repository (eg: private, Github etc).

The list goes on, but the above is the major points.


fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal

My public PGP key:  http://tinyurl.com/graeme-pgp

More information about the fpc-pascal mailing list