All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wincent Colaiuta <win@wincent.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: (Ab)using filter-branch from a post-receive hook
Date: Sun, 15 Jul 2012 01:17:13 -0700	[thread overview]
Message-ID: <11BD88E2-F82C-4CD9-8EA3-1CF263D7C53A@wincent.com> (raw)
In-Reply-To: <7va9z15xrc.fsf@alter.siamese.dyndns.org>

On Jul 14, 2012, at 11:44 PM, Junio C Hamano wrote:

> Wincent Colaiuta <win@wincent.com> writes:
> 
>> On Jul 14, 2012, at 10:25 PM, Junio C Hamano wrote:
>> 
>>> I did not see anything wrong doing what you described in the
>>> post-receive, even though having the hook in the "scratch" felt
>>> strange, as the "copying from authoritative" would also want to be
>>> automated and the natural triggering mechanism to do so would be a
>>> post-receive there.  What issues were you worried about?
>> 
>> The part that I left out, to keep things simple, is that ...
> 
> I said "strange", not "wrong".  If it is undesirable to hook the
> "authoritative" repository, it is perfectly fine to hook on the
> receiving end.
> 
> So what issues were you worried about?

I guess I was just a little worried about using filter-branch in a completely automated context (I have used it previously, but always in a manual fashion to do explicit "surgery" on the history), so I really just wanted a sanity check. Thanks for your input; it's much appreciated.

We have a strict fast-forward-only policy on our master branch, so I think the hook will be quite simple to write and won't require us to handle any crazy edge cases.

Cheers,
Wincent

      reply	other threads:[~2012-07-15  8:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-15  4:01 (Ab)using filter-branch from a post-receive hook Wincent Colaiuta
2012-07-15  5:25 ` Junio C Hamano
2012-07-15  5:50   ` Wincent Colaiuta
2012-07-15  6:44     ` Junio C Hamano
2012-07-15  8:17       ` Wincent Colaiuta [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=11BD88E2-F82C-4CD9-8EA3-1CF263D7C53A@wincent.com \
    --to=win@wincent.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.