suggestion on the hook
design is
welcome. Also this can be implemented on the above hook or in a separate hook.
A separate hook is better due to maintainability and then I need to call
multiple
pre-receive hook. Please suggest.
Thanks
On 18-Mar-2013, at 11:14 AM, Joydeep Bakshi
wrote:
&g
On 15-Mar-2013, at 6:44 PM, Magnus Bäck wrote:
>>
>
> Right, but that's R/W permissions. Almost any piece of Git hosting
> software supports restriction of pushes. Discriminating *read* access
> between developers and maintenance people sounds like a disaster if it's
> the same organisation.
Hello list,
I have implemented git pre-received hook successfully. And it works on the repo
level.
Could anyone suggest how to call branch level hook please ?--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info
On 15-Mar-2013, at 6:14 PM, Fredrik Gustafsson wrote:
> On Fri, Mar 15, 2013 at 05:54:05PM +0530, Joydeep Bakshi wrote:
>> [1] the server will have different git repo with branches
>> [2] there will be a web-based GUI which must be flexible to show just a
>> specific bran
forgot to mention:
a code review system like gerrit is also helpful, but don't know if gerrit
has such fine control mechanism.
On 15-Mar-2013, at 5:54 PM, Joydeep Bakshi
wrote:
> Hello list,
>
> Greetings !!!
>
> I'm building a git r
Hello list,
Greetings !!!
I'm building a git repo on a dedicated server; hence need some kind guidelines
from you.
[1] the server will have different git repo with branches
[2] there will be a web-based GUI which must be flexible to show just a
specific branch of a repo based on user authentic
6 matches
Mail list logo
