From: David Lang <david@lang.hm>
To: "Deniz Türkoglu" <deniz@spotify.com>
Cc: Krzysztof Mazur <krzysiek@podlesie.net>,
Thiago Farina <tfransosi@gmail.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Shawn Pearce <sop@google.com>
Subject: Re: Reviews on mailing-list
Date: Sun, 11 Nov 2012 16:43:05 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1211111642030.19687@nftneq.ynat.uz> (raw)
In-Reply-To: <CA+ZXwZMh=ON4g32nRHD5cMTX1c7ohhqhXHUNdh57BMvSHG0cYA@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 656 bytes --]
On Sun, 11 Nov 2012, Deniz Türkoglu wrote:
> I understand from the feedback that gerrit should get better on making
> it possible to review code via e-mail, as pointed out in Nguyen's
> mail, a flow like Shawn mentioned[1] can be a good solution.
>
> FWIW, I can fetch the change(s) from gerrit I am interested in and
> review it any time I want. I currently have many checked out topics I
> am working on for instance.
That requires that you know before you loose connectivity what changes you want
to review.
With e-mail based reviews, you just pull copies of all your mail and it includes
any pending reviews along with everything else.
David Lang
next prev parent reply other threads:[~2012-11-12 0:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 23:19 Reviews on mailing-list Deniz Türkoglu
2012-11-10 23:40 ` Felipe Contreras
2012-11-11 1:13 ` Thiago Farina
2012-11-11 5:54 ` Junio C Hamano
2012-11-11 11:11 ` suvayu ali
2012-11-11 12:02 ` Nguyen Thai Ngoc Duy
2012-11-11 12:14 ` Felipe Contreras
2012-11-11 13:09 ` Thiago Farina
2012-11-11 13:40 ` Felipe Contreras
2012-11-11 17:14 ` Krzysztof Mazur
2012-11-11 21:15 ` David Lang
2012-11-12 0:35 ` Deniz Türkoglu
2012-11-12 0:43 ` David Lang [this message]
2012-11-13 13:38 ` Nguyen Thai Ngoc Duy
2012-11-11 1:28 ` Deniz Türkoglu
2012-11-11 12:24 ` Felipe Contreras
2012-11-11 7:26 ` Ramkumar Ramachandra
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1211111642030.19687@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=deniz@spotify.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=krzysiek@podlesie.net \
--cc=sop@google.com \
--cc=tfransosi@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).