From: Wincent Colaiuta <win@wincent.com>
To: Jeff King <peff@peff.net>
Cc: Andreas Ericsson <ae@op5.se>, Russ Brown <pickscrape@gmail.com>,
git@vger.kernel.org
Subject: Re: Workflow question
Date: Tue, 25 Sep 2007 22:37:10 +0200 [thread overview]
Message-ID: <5E384CBB-4562-47B3-B4D8-D12D5A5129D6@wincent.com> (raw)
In-Reply-To: <20070925202022.GC19549@segfault.peff.net>
El 25/9/2007, a las 22:20, Jeff King escribió:
> On Tue, Sep 25, 2007 at 09:50:34PM +0200, Wincent Colaiuta wrote:
>
>> Google has a pretty interesting internal code review system:
>>
>> <http://video.google.com/videoplay?docid=-8502904076440714866>
>
> Interesting pointer, thanks. Though I did get a little concerned
> when I
> saw that it is based on Perforce. ;)
Yes (poor Google employees!), and not only that, I'm not aware of any
public access to the code. But still, there are some interesting
ideas about the review process in there.
W
next prev parent reply other threads:[~2007-09-25 20:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 16:43 Workflow question Russ Brown
2007-09-25 19:09 ` Andreas Ericsson
2007-09-25 19:34 ` Jeff King
2007-09-25 19:50 ` Wincent Colaiuta
2007-09-25 20:20 ` Jeff King
2007-09-25 20:37 ` Wincent Colaiuta [this message]
2007-09-25 19:42 ` Russ Brown
2007-09-25 20:17 ` Jeff King
2007-09-25 20:56 ` Russ Brown
2007-09-25 21:28 ` Junio C Hamano
2007-09-26 0:01 ` Russ Brown
2007-09-26 0:47 ` Jeff King
2007-09-26 1:51 ` Karl Hasselström
2007-09-26 2:55 ` Russ Brown
2007-09-26 5:29 ` Junio C Hamano
2007-09-26 12:42 ` Jeff King
2007-09-25 22:38 ` Andreas Ericsson
-- strict thread matches above, loose matches on Subject: below --
2007-07-24 13:53 workflow question Patrick Doyle
2007-07-24 15:37 ` Alex Riesen
2007-07-24 16:30 ` Patrick Doyle
2007-07-24 16:35 ` Julian Phillips
2007-07-24 20:54 ` Alex Riesen
2007-07-24 20:57 ` Alex Riesen
2007-07-24 21:00 ` J. Bruce Fields
2007-07-24 21:38 ` Linus Torvalds
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=5E384CBB-4562-47B3-B4D8-D12D5A5129D6@wincent.com \
--to=win@wincent.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=pickscrape@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).