From: "Alexander Gladysh" <agladysh@gmail.com>
To: "Paolo Bonzini" <bonzini@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: What is the pre-merge hook status?
Date: Sun, 19 Oct 2008 10:51:33 +0400 [thread overview]
Message-ID: <c6c947f60810182351n444d19bew41f507c04d24fdd0@mail.gmail.com> (raw)
In-Reply-To: <48FA5BBB.8060406@gnu.org>
On Sun, Oct 19, 2008 at 1:57 AM, Paolo Bonzini <bonzini@gnu.org> wrote:
> > What is the status of your pre-merge hook patch?
> >
> > http://article.gmane.org/gmane.comp.version-control.git/93888
> >
> > I think it can help me greatly with my repository management process.
>
> I decided that it was a bad design for me at least, because the control
> had better be implemented on the server (using an update hook). But I
> can submit it if you need it for something.
Please do. I've found that things in newbie user repo may become way
too entangled before branch gets to server. My users need an
early-warning system.
Thanks,
Alexander.
prev parent reply other threads:[~2008-10-19 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 6:42 What is the pre-merge hook status? Alexander Gladysh
2008-10-18 21:57 ` Paolo Bonzini
2008-10-19 6:51 ` Alexander Gladysh [this message]
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=c6c947f60810182351n444d19bew41f507c04d24fdd0@mail.gmail.com \
--to=agladysh@gmail.com \
--cc=bonzini@gnu.org \
--cc=git@vger.kernel.org \
/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).