git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What is the pre-merge hook status?

From
Alexander Gladysh <agladysh@gmail.com>
Date
Oct 19, 2008, 06:51 UTC
Message-ID
<c6c947f60810182351n444d19bew41f507c04d24fdd0@mail.gmail.com>
In-Reply-To
<48FA5BBB.8060406@gnu.org>
On Sun, Oct 19, 2008 at 1:57 AM, Paolo Bonzini <bonzini@gnu.org> wrote:
Show 9 quoted lines
> > 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.

Previous: Paolo Bonzini
Message 3 of 3 in “What is the pre-merge hook status?”
  1. Alexander GladyshOct 18, 2008
  2. Paolo BonziniOct 18, 2008
  3. Alexander GladyshOct 19, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.