Greg> On Mon, Apr 15, 2013 at 05:13:45PM -0700, D M German wrote:
>>
>>
>> Greg KH twisted the bytes to say:
>>
>> >> http://o.cs.uvic.ca:20810/perl/next.pl
>>
Greg> Yes, that's a great thing. Maybe the ability to see the sub
Greg KH twisted the bytes to say:
>> http://o.cs.uvic.ca:20810/perl/next.pl
Greg> Yes, that's a great thing. Maybe the ability to see the subject: line
Greg> of the commit somewhere easier than having to click through to the patch
Greg> would be nice, so we can just glance at the report a
Greg KH twisted the bytes to say:
Greg> But, for the linux-next stuff, that could be very interesting. We
Greg> always like seeing what commits in a -rc1 release did NOT previously
Greg> show up in linux-next. Stephen has some tools on how to do this, it
Greg> would be interesting to see i
D M German twisted the bytes to say:
dmg> One thing that will help me is that if any of you feel I am not tracking
dmg> your repository, please send me an email with its address.
dmg> thank you!
dmg> --daniel
I have now listed all the repositories I am tracking:
http://o.cs.u
vinod>
vinod>
vinod>
vinod> On Fri, 2013-04-12 at 13:22 -0700, D M German wrote:
vinod> > Hi Everybody,
vinod> >
vinod> > I am professor of computer science at the University of Victoria
vinod> > (Canada).
vinod> >
vinod> > During
Hi Everybody,
I am professor of computer science at the University of Victoria
(Canada).
During the last year and a half, we have been trying to track the
commits as they move in the entire linux git repos ecosystem. We have
amassed a good amount of data that tell us for every commit (and in fac
6 matches
Mail list logo