From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
Tom Tromey <tom@tromey.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: some thoughts on gerrit
Date: Mon, 21 Oct 2019 20:59:00 -0000 [thread overview]
Message-ID: <CAPTJ0XHa97vx+pBPnkn7jJPqQ0eC4mP+2HOhuQbNN43QzwN9jQ@mail.gmail.com> (raw)
In-Reply-To: <mvmh842a2te.fsf@suse.de>
FWIW, I filed https://bugs.chromium.org/p/gerrit/issues/detail?id=11791
and reopened https://bugs.chromium.org/p/gerrit/issues/detail?id=924
Christian
On Mon, Oct 21, 2019 at 4:03 AM Andreas Schwab <schwab@suse.de> wrote:
>
> On Okt 20 2019, Sergio Durigan Junior wrote:
>
> > doesn't apply, so I can't comment on it. My workflow is likely to stay
> > the same: git-new-workdir, hack, submit (either via gerrit or git
>
> Consider using git worktree instead, git-new-workdir is obsolete.
>
> Andreas.
>
> --
> Andreas Schwab, SUSE Labs, schwab@suse.de
> GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
> "And now for something completely different."
next prev parent reply other threads:[~2019-10-21 20:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 14:37 Tom Tromey
2019-10-20 22:25 ` Sergio Durigan Junior
2019-10-20 22:30 ` Sergio Durigan Junior
2019-10-21 9:02 ` Andreas Schwab
2019-10-21 20:59 ` Christian Biesinger via gdb-patches [this message]
2019-10-21 21:24 ` Sergio Durigan Junior
2019-10-21 21:25 ` Sergio Durigan Junior
2019-10-20 23:17 ` Andrew Pinski
2019-10-21 1:49 ` Simon Marchi
2019-10-21 3:26 ` Simon Marchi
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=CAPTJ0XHa97vx+pBPnkn7jJPqQ0eC4mP+2HOhuQbNN43QzwN9jQ@mail.gmail.com \
--to=gdb-patches@sourceware.org \
--cc=cbiesinger@google.com \
--cc=schwab@suse.de \
--cc=sergiodj@redhat.com \
--cc=tom@tromey.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