public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Matt Rice <ratmice@gmail.com>, Luis Machado <luis.machado@linaro.org>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Regressions getting more common
Date: Wed, 14 Oct 2020 10:46:23 -0400	[thread overview]
Message-ID: <1803667a-1281-9e8c-147c-ead91db2c3f9@simark.ca> (raw)
In-Reply-To: <CACTLOFrC=VKNEphuyL6fsCJihSh=eQcc6n_L42eTi2wb-mBxYA@mail.gmail.com>


On 2020-10-13 9:13 p.m., Matt Rice via Gdb wrote:
> Speaking of gerrit, I noticed that the server side git hooks, used by
> https://git-repo.info/
> for its repo -upload/git pull-request functionality has landed in git master,
> and is slated to be in the next git release...
>
> https://git.kernel.org/pub/scm/git/git.git/commit/?id=6c430a647cb990fc856d328733fa59e1fafadb97
>
> Which seems like an interesting new approach for this stuff.

Interesting.  If I understand correctly, this allows implementing
something similar to Gerrit's magic branches, where when you push to it,
a script/hook on the  server can do something arbitrary with it?

In any case, I don't think we'll want to develop anything new here, that
wouldn't be a very good way to spend our time.  But perhaps this will
lead to useful tools being developed in the future.

Simon

  reply	other threads:[~2020-10-14 14:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 17:05 Luis Machado
2020-10-14  1:13 ` Matt Rice
2020-10-14 14:46   ` Simon Marchi [this message]
2020-10-14 15:49     ` Matt Rice
2020-10-14 14:41 ` Simon Marchi
2020-10-14 15:50   ` Rainer Orth
2020-10-14 19:03   ` Sergio Durigan Junior
2020-10-15 12:55   ` Luis Machado
2020-10-16  0:29     ` Simon Marchi
2020-10-14 15:14 ` Kamil Rytarowski

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=1803667a-1281-9e8c-147c-ead91db2c3f9@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb@sourceware.org \
    --cc=luis.machado@linaro.org \
    --cc=ratmice@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).