Please avoid git-push style drops of 50+ commits....

[Justin Holewinski]

Alright, I'll figure something out.  Ordinarily, I would commit when ready;
but for these upstreaming patches there is an approval process that acts
like a barrier/sync point. :)


On Fri, Jun 27, 2014 at 3:46 PM, Chandler Carruth <chandlerc at google.com>
wrote:

>
> On Fri, Jun 27, 2014 at 9:36 PM, Justin Holewinski <
> justin.holewinski at gmail.com> wrote:
>
>> Sorry, I'll try to limit the commit frequency in the future.  For
>> reference, what would you recommend for spacing out larger collections of
>> patches?  15 minutes per 3?  30 minutes per 5?
>
>
> I would commit when ready rather than batching at all.
>
> If it isn't possible for you to commit them incrementally, then I would
> probably watch the bots cycle between commits or something? I have no idea
> how to do that reasonably. The entire workflow is really optimized for
> committing patches as they become ready to commit.
>



-- 

Thanks,

Justin Holewinski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140627/c434d6d7/attachment.html>