From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Mario Pareja" <mpareja.dev@gmail.com>
Cc: "Andreas Ericsson" <ae@op5.se>, "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Locking binary files
Date: Tue, 23 Sep 2008 16:28:00 +0200 [thread overview]
Message-ID: <81b0412b0809230728p4e81572bg67a3bec4c32c7dfb@mail.gmail.com> (raw)
In-Reply-To: <94c1db200809230656q4a9a765dw2354c0058b1d940c@mail.gmail.com>
2008/9/23 Mario Pareja <mpareja.dev@gmail.com>:
>> So it's a communication issue then.
>
> Yes, but I think the communication of this information needs to happen
> as part of a developers normal work-flow rather than requiring them to
> remember to check an external system.
Look at pre-receive and update hooks. They can deny a push operation and
get enough information to notice a change to the path of your unlucky file.
And yes, *you* have to do that yourself.
next prev parent reply other threads:[~2008-09-23 14:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94c1db200809222333q4953a6b9g8ce0c1cd4b8f5eb4@mail.gmail.com>
2008-09-23 6:39 ` Locking binary files Mario Pareja
2008-09-23 7:18 ` Andreas Ericsson
[not found] ` <94c1db200809230054t20e7e61dh5022966d4112eee6@mail.gmail.com>
2008-09-23 8:31 ` Andreas Ericsson
2008-09-23 13:56 ` Mario Pareja
2008-09-23 14:28 ` Alex Riesen [this message]
2008-09-23 17:32 ` Daniel Barkalow
2008-09-23 19:49 ` Junio C Hamano
2008-09-23 21:13 ` Daniel Barkalow
2008-09-23 21:54 ` Dmitry Potapov
2008-09-23 22:29 ` Daniel Barkalow
2008-09-23 23:21 ` Dmitry Potapov
2008-09-24 4:15 ` Daniel Barkalow
2008-09-24 15:00 ` Dmitry Potapov
2008-09-23 20:46 ` Dmitry Potapov
2008-09-23 11:16 ` Boaz Harrosh
2008-09-23 11:20 ` Boaz Harrosh
2008-09-23 14:14 ` Mario Pareja
2008-09-23 14:35 ` Boaz Harrosh
2008-09-23 13:44 ` Dmitry Potapov
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=81b0412b0809230728p4e81572bg67a3bec4c32c7dfb@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=mpareja.dev@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).