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 subject: line
Greg> of the commit somewhere easier than
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 subject: line
Greg of the commit somewhere easier than having to click
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 subject: line
> Greg> of the commit somewhere easier than having to click
Hi Daniel,
On Sat, Apr 13, 2013 at 11:01:24AM -0700, D M German wrote:
> 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> >
Hi Daniel,
On Sat, Apr 13, 2013 at 11:01:24AM -0700, D M German wrote:
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
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 subject: line
Greg of the commit somewhere easier than having to click through to the
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
On Mon, Apr 15, 2013 at 02:49:34PM -0700, D M German wrote:
>
>
> 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.
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
On Mon, Apr 15, 2013 at 11:21:32AM -0700, dmg wrote:
> Hi Ben,
>
> On 4/13/13, Ben Hutchings wrote:
[...]
> > It should be possible to find such backported commits based on a simple
> > regex search over the commit message:
>
> I took a more aggressive approach. I decided to look for 40 length
Hi Ben,
On 4/13/13, Ben Hutchings wrote:
> I notice that where a commit is cherry-picked cleanly on a stable
> branch, like 6b90466cfec2a2fe027187d675d8d14217c12d82, your script finds
> the corresponding commit on the stable branch. This is useful.
>
> But where some backporting changes are
Hi Ben,
On 4/13/13, Ben Hutchings b...@decadent.org.uk wrote:
I notice that where a commit is cherry-picked cleanly on a stable
branch, like 6b90466cfec2a2fe027187d675d8d14217c12d82, your script finds
the corresponding commit on the stable branch. This is useful.
But where some backporting
On Mon, Apr 15, 2013 at 11:21:32AM -0700, dmg wrote:
Hi Ben,
On 4/13/13, Ben Hutchings b...@decadent.org.uk wrote:
[...]
It should be possible to find such backported commits based on a simple
regex search over the commit message:
I took a more aggressive approach. I decided to look for
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 if
On Mon, Apr 15, 2013 at 02:49:34PM -0700, D M German wrote:
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
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 and
I notice that where a commit is cherry-picked cleanly on a stable
branch, like 6b90466cfec2a2fe027187d675d8d14217c12d82, your script finds
the corresponding commit on the stable branch. This is useful.
But where some backporting changes are needed, such as for
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:
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 the last year and a half, we have been trying to
On Fri, 2013-04-12 at 13:22 -0700, D M German wrote:
> 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
>
On Fri, 2013-04-12 at 13:22 -0700, D M German wrote:
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
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 the last year and a half, we have been trying to track the
vinod
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:
I notice that where a commit is cherry-picked cleanly on a stable
branch, like 6b90466cfec2a2fe027187d675d8d14217c12d82, your script finds
the corresponding commit on the stable branch. This is useful.
But where some backporting changes are needed, such as for
On Fri, Apr 12, 2013 at 01:22:09PM -0700, D M German wrote:
>
> 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
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
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
On Fri, Apr 12, 2013 at 01:22:09PM -0700, D M German wrote:
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
28 matches
Mail list logo