quot; file. Another example, if a VO file is
> updated, then there will be a db migration file added as well.
> Cool work,
>
> On Thu, Dec 10, 2015 at 9:21 AM, Igor Wiese wrote:
>
> > Hi Sebastien.
> >
> > We used only 141 commits because we needed data fro
past time.
It is in my plan to use also data from github to make the dataset more
complete.
All the best,
2015-12-10 11:22 GMT-02:00 sebgoa :
>
> On Dec 10, 2015, at 12:31 AM, Igor Wiese wrote:
>
> > Hi, Cloudstack Community.
> >
> > My name is Igor Wiese, phd Student
oming changes.
The main ideia is "avoid" the incomplete change that could causes a new bug
can appeared, or avoid waisting time to inspect files/debugging system to
find files to change in a issue.
What do you think?
All the best,
Igor Wiese
2015-12-10 10:55 GMT-02:00 Vadim Kimlay
all of them are in the commit.
All the best,
Igor Wiese
2015-12-10 7:11 GMT-02:00 Anshul Gangwar :
> Before giving feedback I have some questions
>
> 1) What do you mean by "correctly predict 60% commits”?
> 2) What are the feature measures you are giving as input here to syst
Hi, Cloudstack Community.
My name is Igor Wiese, phd Student from Brazil. In my research, I am
investigating two important questions: What makes two files change
together? Can we predict when they are going to co-change again?
I've tried to investigate this question on the Cloudstack pr
