Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Existing git repository and project explorer
Message
De
02/03/2021 10:20:10
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Allemagne
 
 
À
02/03/2021 10:08:40
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
Information générale
Forum:
Visual FoxPro
Catégorie:
VFPX/Sedna
Divers
Thread ID:
01678626
Message ID:
01678655
Vues:
42
>>or
>>
>>git commit -a
>>
>>git will gather all changes and commit. Files not changed will not be touched.
>>The same way is to get to an old state via git checkout.
>>The idea is to get the whole state of the project at once
>>There are ways to get single files too, but this is not for day to day work.
>
>From my experience, not too good for VFP. Because of the files you may have touched and didn't actually change anything, but since they contain an ActiveX reference (or other COM), some kind of reference ID, a GUID or whatever in one of the field changes behind the scenes, and that marks the file as changed.
>I know some versions of scctextX have the ability to ignore that (by not including that field in the first place), but I still don't think it's good enough.
>I prefer to have granular control, i.e. to know exactly which files I'm committing, and in case of doubt (was this any change I made, what's going on here? and such) I'd force myself to doublecheck the differences before either checking in my version, or getting the repository version. On a team of 4-5 people, this reduced the number of snafus to one or two a year, which was great.
>With any kind of blind reliance on timestamps, I'd expect that to be once a month at least.

I use FoxBin2Prg in company with own Bin2Text (all on VFPX), just creating text out of the table-based sources. Only storing text and recreating bin from text. Just now switching to do this for DBF/ DBC too (I will push out a fork of FoxBin2Prg fixing some bugs this month).
Works like a charm - and I'm heavy into branching, subtrees.
The only dangerous thing is to remember to generate the f.. binaries after tricky merges.

Even if some odd COM / Active X is changing - the commit is tiny, it's only the text snippet. It needs time to generate the text file, but I use a sort of hashing to process a minimum of binaries. So I just start the text generation for whole PJX and it's finished in a small number of seconds.
Just hitting 3 keys and enter a commit message. (ok, I have auto-generated to merge-squeeze later, but this a different show.) No point'n'click adventure.

;)
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform