On Thu, Nov 14, 2013 at 07:22:23PM -0200, Otavio Salvador wrote:
On Thu, Nov 14, 2013 at 7:17 PM, Tom Rini trini@ti.com wrote:
On Thu, Nov 14, 2013 at 12:59:05PM -0800, Vadim Bendebury (????) wrote:
On Thu, Nov 14, 2013 at 11:54 AM, Tom Rini trini@ti.com wrote:
On Tue, Nov 12, 2013 at 11:46:35AM -0800, Vadim Bendebury (????) wrote:
Hello Wolfgang,
[snip]
Can you not pick up the patches directly from the mailing list? I mean, we know of the problems patchwork has (like silently dropping certain base64 / utf8 encoded messages), so we should rather try and get a more reliable feed for the patches?
this is the thing: picking up patches from patchwork is not something you'd do regularly - this is just my way of populating the review site from a single test account.
If this workflow were adopted, each user would push their patch to the gerrit server, creating a new review branch for that particular patch. In general, gerrit view of the branch matches the submitter's view of the branch - if the submitter has several patches in one branch, they will all be uploaded by gerrit to the same separate branch, maintaining the relationship between the patches.
This is my biggest concern. On the one-off to infrequent contribution side (and we do have some of that), I worry about the infrastucture hurdle here.
Sorry, I am not sure i understand what the biggest concern is: that the users would push their own patches? Why is this a problem - the patches would go into their own branches until reviewed and merged. Or did you mean something else?
I mean, it's a higher hurdle to clear. Looking at other non-Android projects, I know some folks have said "bah, not worth the effort" to push trivial things, if it must come via gerrit. So some way to scrape the ML for things that don't come in via gerrit to start with would be handy.
I think this is something one of 'known' developers will end doing and applying it to Gerrit.
I suspect you're right, and that it would end up being me. So I'm fishing for something else, at least a little bit longer.