From: "Shawn O. Pearce" <spearce@spearce.org>
To: Joshua Jensen <jjensen@workspacewhiz.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Deleting of the specified ref during the post-receive hook
Date: Tue, 21 Sep 2010 09:00:24 -0700 [thread overview]
Message-ID: <20100921160024.GI32601@spearce.org> (raw)
In-Reply-To: <4C98D558.9090900@workspacewhiz.com>
Joshua Jensen <jjensen@workspacewhiz.com> wrote:
> Let's ignore the review+submit portion of Gerrit now. Can Gerrit be
> coaxed to take a refs/for/master and directly apply it to the master
> branch WITHOUT the review cycle? If so, then I'm wasting my time trying
> to right a script.
Nope. But only because nobody has proposed doing that before.
Its not impossible to do...
--
Shawn.
prev parent reply other threads:[~2010-09-21 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 14:40 Deleting of the specified ref during the post-receive hook Joshua Jensen
2010-09-21 14:50 ` Shawn O. Pearce
2010-09-21 15:55 ` Joshua Jensen
2010-09-21 16:00 ` Shawn O. Pearce [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=20100921160024.GI32601@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=jjensen@workspacewhiz.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 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).