Hi, Chris
Back when I was really working, I did the pretty much the same thing, using 
Mercurial with the Tortoise interface, and was very impressed with the way it 
worked.  Git seems to be gaining share over Mercurial, but they both work well.
I'm kind of curious about the benefit you hope to gain by excluding binary 
files.  In my case, I decided to leave things as they were and include all the 
files, binary or not, until I saw a problem.  Yes, I couldn't see the inside of 
the binaries to verify the exact change, but I found I didn't need to.  The 
source control tells you that it changed, which is the important part, and in 
the case of an SCX, the SCT, which is NOT binary, will pretty much tell you 
which changes you made at that point.
I found the reported change info completely adequate, and it seems to me that 
converting binaries to text and including them instead, in addition to being a 
cumbersome extra step, is creating a new place to make mistakes.  The great 
thing about distributed source control is that it makes it EASY to record the 
version changes, adding extra steps gives an incentive to skip the commitment.
Dan Covill

> From: [email protected]
> To: [email protected]
> Subject: Source Control / VFP
> Date: Sat, 28 Jun 2014 08:55:44 +0000
> 
> Hi All
> 
> We are moving over to source control, for one reason or another we will be 
> using Git hosted on Github.  Our chosen GUI at the moment is SourceTree.
> 
> We are planning on excluding binary files i.e. SCX,PJX etc.
> 
> Looking now to a tool which will convert our binary files to text so that we 
> can benefit from the power of the system I have discovered FOX2BIN on VFPX.
> 
> This seems to work well although I have only tested on our test project.
> 
> Leading on to my question ...
> 
> What's the best way to manage this at the Working Copy level?
> 
> Is it just a case of remembering to perform a conversion back from the text 
> versions to binary versions before starting making changes to the project?
> Should I be including all the binary files as well and only using the text 
> versions for information purposes?
> Could I maybe included the PJX and a project hook to automatically do the 
> conversion either way upon file open and close?
> 
> Basically I don't want to bloat the repository with lots of binary files, but 
> want a fellow developer the other end to be able to clone it and load fox and 
> start with modi proj ? without having to remember to convert this, that or 
> the other.
> 
> Any thoughts welcomed.

                                          

--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to