From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Nicolas Adenis-Lamarre <nicolas.adenis.lamarre@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Locking files / git
Date: Tue, 17 Sep 2013 23:36:19 +0200 [thread overview]
Message-ID: <20130917213619.GM28675@paksenarrion.iveqy.com> (raw)
In-Reply-To: <CACPGbcsB-ieZnS5maQgtnRTifFON9fEFpCGGdHtQ2ZjySdxDYA@mail.gmail.com>
On Tue, Sep 17, 2013 at 09:45:26PM +0200, Nicolas Adenis-Lamarre wrote:
> 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
next prev parent reply other threads:[~2013-09-17 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 19:45 Locking files / git Nicolas Adenis-Lamarre
2013-09-17 21:00 ` Jeff King
2013-09-17 21:36 ` Fredrik Gustafsson [this message]
2013-09-18 10:12 ` Nicolas Adenis-Lamarre
2013-09-18 21:12 ` Sitaram Chamarty
2013-09-18 19:06 ` Thomas Koch
2013-09-18 21:04 ` Sitaram Chamarty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130917213619.GM28675@paksenarrion.iveqy.com \
--to=iveqy@iveqy.com \
--cc=git@vger.kernel.org \
--cc=nicolas.adenis.lamarre@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).