From: Anca Emanuel <anca.emanuel@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git <git@vger.kernel.org>, sop <sop@google.com>
Subject: Re: Google Gerrit
Date: Tue, 2 Mar 2010 21:22:21 +0200 [thread overview]
Message-ID: <c1fb08351003021122wcd390bracd2a61f1355c5d6@mail.gmail.com> (raw)
In-Reply-To: <4B8D2F17.8040305@drmicha.warpmail.net>
> Maybe, one of the main Git guys here should look into it - such as the
> one you cc'ed and who's one of the main Gerrit guys also?
>
> Seriously, are you suggesting to use Gerrit for the management of
> git.git (the Git source), or what is this post about? Also, please don't
> crosspost. If you think kernel people should use Gerrit, post there only.
>
> Michael
>
Hi, Michael:
I know the tools are not matured yet, this is just an buzz about.
But in the future, I like to see lkml on wave and remote servers for
testing online and in "real time", etc. It's a dream ?
prev parent reply other threads:[~2010-03-02 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 14:10 Google Gerrit Anca Emanuel
2010-03-02 15:26 ` Shawn O. Pearce
2010-03-02 15:30 ` Michael J Gruber
2010-03-02 19:22 ` Anca Emanuel [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=c1fb08351003021122wcd390bracd2a61f1355c5d6@mail.gmail.com \
--to=anca.emanuel@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=sop@google.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).