From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Stefan Beller <sbeller@google.com>
Cc: git@vger.kernel.org, kostix+git@007spb.ru,
hackerp@suddenlink.net, sitaramc@gmail.com
Subject: Re: git lock files (Was: GIT for Microsoft Access projects)
Date: Wed, 10 Jun 2015 09:47:33 +0200 [thread overview]
Message-ID: <20150610074733.GM30511@paksenarrion.iveqy.com> (raw)
In-Reply-To: <1433870383-7631-1-git-send-email-sbeller@google.com>
On Tue, Jun 09, 2015 at 10:19:43AM -0700, Stefan Beller wrote:
> Just because Git allows distributed workflows, doesn't mean we
> should only focus on being distributed IMHO.
>
> The question for content not being mergable easily pops up all
> the time. (Game/Graphics designers, documents, all this binary
> stuff, where there is no good merge driver).
>
> I could imagine a "git lock" command which looks like this:
You do know that gitolite has locking functionality?
--
Fredrik Gustafsson
phone: +46 733-608274
e-mail: iveqy@iveqy.com
website: http://www.iveqy.com
next prev parent reply other threads:[~2015-06-10 7:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 14:45 GIT for Microsoft Access projects hackerp
2015-06-08 16:14 ` Konstantin Khomoutov
2015-06-08 22:02 ` Randall S. Becker
2015-06-09 13:54 ` Sitaram Chamarty
2015-06-09 17:19 ` git lock files (Was: GIT for Microsoft Access projects) Stefan Beller
2015-06-09 18:21 ` hackerp
2015-06-09 18:50 ` Konstantin Khomoutov
2015-06-09 19:08 ` Stefan Beller
2015-06-10 7:47 ` Fredrik Gustafsson [this message]
2015-06-10 15:22 ` Stefan Beller
2015-06-10 16:32 ` git lock files Junio C Hamano
2015-06-15 8:52 ` Thomas Koch
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=20150610074733.GM30511@paksenarrion.iveqy.com \
--to=iveqy@iveqy.com \
--cc=git@vger.kernel.org \
--cc=hackerp@suddenlink.net \
--cc=kostix+git@007spb.ru \
--cc=sbeller@google.com \
--cc=sitaramc@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).