[Gambas-devel] Fwd: Re: Gambas to Git(Lab)

Christof Thalhofer chrisml at ...757...
Sun Jul 23 12:02:30 CEST 2017


Am 23.07.2017 um 01:33 schrieb Benoît Minisini via Gambas-devel:

> The problem I encountered when moving from subversion to git in my job 
> is that git does not really have tags and branches that behave the same 
> way. I.e. being actual independent trees.
> 
> A recently added feature named "working tree" in git seems to help to do 
> the same thing: developing on different versions at the same time.

I did not use that feature, as I only switch between different branches
in my code (maybe one for each release). But it seems to have advantages
if you have very big repositories (where switching between branches
costs too much time):

https://stackoverflow.com/questions/31935776/what-would-i-use-git-worktree-for

> Or maybe I didn't understand how to use git for that?

Here is a good explanation of common git workflows:
https://www.atlassian.com/git/tutorials/comparing-workflows

Why do you want to develop in different versions at the same time, to
fix bugs? Look at "Maintenance Branches" and "Hotfix", maybe that is,
what you wanted to do?

I am unsure what sort of development workflow would be the best for Gambas.

If I look at a big projekt for example that put its codebase to Git –
OTRS – they did it so:

https://github.com/OTRS/otrs

Look there at the branches and tags. They seem to have ongoing
development in master with branches for the "big" releases. Tags are
used to point to subreleases.


Alles Gute

Christof Thalhofer

-- 
Dies ist keine Signatur

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.gambas-basic.org/pipermail/devel/attachments/20170723/5d500b5c/attachment.sig>


More information about the Devel mailing list