On 02/08/2012 04:34 PM, Itamar Heim wrote:
All emails should go to the -patches lists, these would include initial
patch email, comments and commit - but yes, they do not include the
payload.
It doesn't include the inline, since we had some issues contributing that
code to gerrit upstream (well, their gerrit was down, then some CLA issues
- hopefully all resolved by now).
Ah, okay. Now that I look more closely, I guess I can see that you're right re:
everything getting posted.
But it's fairly difficult to see because the subject is the same and the typical
style of inline replying isn't used. Perhaps the patch you spoke of fixes this.
In short, how can one be a silent observer via a mailing list and get a
good
feeling for what's going on in the project?
Is there a way to make Gerrit send the actual patches to the various
mailing
lists as they're posted for review (along with review comments to those
patches)?
As I mentioned above, we saw this gap as well, and (Gal Hammer) wrote a
patch for gerrit to close it.
But I did not want to build a forked version of our gerrit until these
patches are accepted into upstream gerrit.
Once they do, either will wait for the next version, or just backport this
specific patch to the version we have.
I'm glad to hear this! I'll wait until that gets deployed I guess.
Btw, you can also register in gerrit only to specific project and get the
emails directly, rather than via the mailing list.
I'm happy using a mailing list.
Thanks for the quick response.
Regards,
Anthony Liguori
(login, settings, watched projects, choose per project (or even branch)
granularity to watch new/comment/submit emails.
HTH,
Itamar
_______________________________________________
Arch mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/arch
_______________________________________________
Arch mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/arch
