git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Preventing merges from one branch into others
@ 2013-02-07 19:14 Tim Chase
  2013-02-07 19:38 ` Junio C Hamano
  0 siblings, 1 reply; 2+ messages in thread
From: Tim Chase @ 2013-02-07 19:14 UTC (permalink / raw)
  To: git

[tried IRC to no avail]
I've been trying to find a way to prevent myself from merging a
client-specific branch back into my dev/master branches.  Is there an
easy/straightforward way to do this (perhaps via a hook)?  I didn't
see any sort of "pre-merge" hook script.  Visualized:

  A -> B -> C [dev]
   \
    -> Q -> R -> S [customer-specific]

and I want to ensure that changes Q/R/S never find their way back
into dev.

So I was hoping some sort of "hey, you're an idiot for trying to merge
$CUSTOMER_BRANCH back into dev/master" warning. :-)

-tkc

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Preventing merges from one branch into others
  2013-02-07 19:14 Preventing merges from one branch into others Tim Chase
@ 2013-02-07 19:38 ` Junio C Hamano
  0 siblings, 0 replies; 2+ messages in thread
From: Junio C Hamano @ 2013-02-07 19:38 UTC (permalink / raw)
  To: Tim Chase; +Cc: git

Tim Chase <git@tim.thechases.com> writes:

> ...  I didn't
> see any sort of "pre-merge" hook script.

http://thread.gmane.org/gmane.comp.version-control.git/94111/focus=71069

I think yours is a canonical example of "I do not want to run
command X when these conditions hold", when "these conditions" can
be checked locally _before_ you decide to do X.

While it is theoretically possible to give X a pre-X hook in such a
case, we do not want it to be the first choice to avoid hook bloat.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-02-07 19:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-02-07 19:14 Preventing merges from one branch into others Tim Chase
2013-02-07 19:38 ` Junio C Hamano

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).