Re: Locking files / git
- From
Fredrik Gustafsson <iveqy@iveqy.com>
- Date
- Sep 17, 2013, 21:36 UTC
- Message-ID
- <20130917213619.GM28675@paksenarrion.iveqy.com>
- In-Reply-To
- <CACPGbcsB-ieZnS5maQgtnRTifFON9fEFpCGGdHtQ2ZjySdxDYA@mail.gmail.com>
On Tue, Sep 17, 2013 at 09:45:26PM +0200, Nicolas Adenis-Lamarre wrote:
Show 9 quoted lines
> Ooops. It seems that each time somebody says these two words together,
> people hate him, and he is scorned by friends and family.
>
> For the moment, i want a first feedback, an intermediate between
> "locking is bad" and "ok", but i would prefer in the negativ answer
> something with arguments ("Take CVS as an example of what not to do;
> if in doubt, make the exact opposite decision." is one), and in the
> positiv answer, good remarks about problems with my implementation
> that could make it better.So working with locks and text-files is generally stupid to do with git since you don't use git merging capabilities. Working with binary files in git is stupid because git doesn't handle them very well because they the deltas can't be calculated very good.
It seems to me that if you need to do locking one of the above scenarios is true for you and you should not use git at all.
However, there's always the case when you've a mixed project with both binary and text-files. In that case I believe Jeff gave an excellent answer.
But think twice, are you using git in a sane way? Even a small binary file will result in a huge git repo if it's updated often and the project has a long history.
-- Med vänliga hälsningar Fredrik Gustafsson tel: 0733-608274 e-post: iveqy@iveqy.com