[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GIT version


Am 08.02.25 um 07:17 schrieb BB:
On 8/2/25 9:15 am, Christof Thalhofer wrote:
Am 07.02.25 um 14:05 schrieb Benoît Minisini:

Why do you need to not put a new file in the staging area automatically?

I explained that 2018 and also sent this link this morning:
https://lists.gambas-basic.org/pipermail/user/2018-February/062910.html

I read that post with interest.

Me too :-)

It was from 2018, I forgot about it. It was interesting to see that my way of working hasn't changed, except that I don't use Gitk anymore. I am stuck with Zsh, Guake and tig.

I would suggest that if you are embarking on a new / experimental effort
on an existing project that you create a git branch for that work. Then
all your playing around will be constrained to that branch, which after
due consideration you can either merge or drop as you require. If you
find a change that needs to go into your main branch, then that is
relatively easy as well.

But I reckon you know that already.

Yes, I always create feature branches when I want to realize new ideas, but at the same time am unsure whether they are good.

AFAIC the gambas git handling is fine for me... with the caveat that I
wish that the changes in the history popup would render correctly so the
collapse trigger can be hit with the mouse.

I tried the Git handling of the IDE the first time again since then.

It still does not reflect some of the most important concepts of Git:
The 'staging area' with its possibility to select and collect a couple of changes to compose a commit. The 'stash' that can be used to set aside all changes to forget them or reapply them later. I did not test if it can be used to create branches and if it would be possible to cherry-pick from another branch into the current one.

If you like it as it is, it's fine. For me it lacks important features, as a keyboard junkie I have to grab to the mouse too often to click and scroll so I find it to be slow and it confuses me by highlighting unimportant details (why are the hashes bold and have a colored background? Normally you hardly need a hash, actually only if you do a 'cherry-pick $hash' from another branch or 'reset --hard $hash').

I hope it doesn't look like excessive criticism, it's just the reasons why i don't use it and prefer other approaches.

Alles Gute

Christof Thalhofer

--
Dies ist keine Signatur


Follow-Ups:
Re: GIT versionBB <adamnt42@xxxxxxxxx>
References:
GIT versionPhilippe Valarcher <philippe.valarcher@xxxxxxx>
Re: GIT versionBruce Steers <bsteers4@xxxxxxxxx>
Re: GIT versionPhilippe Valarcher <philippe.valarcher@xxxxxxx>
Re: GIT versiongbWilly <gbWilly@xxxxxxxxxxxxxx>
Re: GIT versionPhilippe Valarcher <philippe.valarcher@xxxxxxx>
Re: GIT versionBruce Steers <bsteers4@xxxxxxxxx>
Re: GIT versionBenoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>
Re: GIT versionChristof Thalhofer <chrisml@xxxxxxxxxxx>
Re: GIT versionChristof Thalhofer <chrisml@xxxxxxxxxxx>
Re: GIT versionBenoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>
Re: GIT versionChristof Thalhofer <chrisml@xxxxxxxxxxx>
Re: GIT versionBB <adamnt42@xxxxxxxxx>