harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Salikh Zakirov <sal...@gmail.com>
Subject Re: [drlvm][PATCH/RFC] GNU Make-based build system for DRLVM -- call for help
Date Sat, 18 Aug 2007 10:46:39 GMT
Salikh wrote:
>> To make the experimentation and contribution to the build system development easier,
>> I've set up a git mirror of DRLVM repository on repo.or.cz. Use following commands
to check out the copy
>>      $ git clone git://repo.or.cz/drlvm.git
>>      $ cd drlvm
>>      $ git checkout -b mob origin/mob

Egor Pasko replied:
> Salikh, GIT mirror of DRLVM is cool (!!!) (I would be glad to use it
> instead of using my own mirror as of today), but contribution back to
> GIT does not follow our process and each patch will have to be
> attached back to JIRA thus requiring duplicate of work, which is not
> very usable.

Okay, you've got the point here. 
Indeed, we need to enforce the same policy on the origin of patches
even the patches are collected in a different repository, so can
apply only the patches from JIRA. 

> I am thinking of a more convenient way to use GIT: run a JIRA crawler
> to collect all patches in JIRA (allowed to include in our sources) and
> apply them to the mirror (add a patch to the experimental branch
> automatically if the patch does not break a set of predefined
> tests). How is that?

A couple of thoughts:
- JIRA crawling automation (finding and downloading patches)
  may be useful to committers, even if they work with SVN only.
- Testing patches for experimental branch requires lots of CPU time,
  i.e. dedicated machine(s), and someone dedicated to keep the scripts
  running -- will we have volunteers for this?

Anyway, the idea sounds promising, I am looking forward to seeing
something concrete.

> And BIG THANKS for working on the build system. I am kinda deadly
> annoyed with current speed. With make we could cook parallel builds
> upto distcc.

"Patches welcome". Seriously, if you think it is useful, please go ahead
and use it. I am pretty sure you'll come up with further improvements soon,
and get it to closer to the state when it can be committed to SVN.

View raw message