On Sat, Jan 23, 2010 at 06:09:36PM -0600, Craig A. Berry wrote:
> On Sat, Jan 23, 2010 at 8:04 AM, Ricardo Signes
> <perl.p5p@rjbs.manxome.org> wrote:
> > * Perl 5 commit summary <nick@ccl4.org> [2010-01-22T21:08:19]
> >> Perl 5 commit summary, activity since Wednesday
> >>
> >> Current branch blead
> >> 21 commits. 6 unique authors. 5 unique committers.
> >> 97 files changed, 1984 insertions(+), 1487 deletions(-)
> >> Net code removal: Nicholas Clark (676 lines)
> >> Thanks, applied: David Golden (1)
> >> Snapshot: http://perl5.git.perl.org/perl.git/snapshot/fe61459e95657c43.tar.gz
> >
> > Is the script that generates this available for mucking about? If not, what
> > I'd really like is to have it provide a git range like deaf0a1..fb0a1b2 so that
> > I could easily run "git log RANGE" and update perldelta based on the full text
> > of the commits, rather than "have to" click all the links below.
> >
> > I realize there are middle grounds, but that would be convenient. This
> > message can serve both as a reminder to update perldelta /and/ a quick note of
> > which changes require review.
It's on dromedary in /home/nicholas/Perl/summary
However, it's not directly generating any ranges, as its comparing the state
of `git show-ref` before and after `git fetch`, against a private repository
clone. There may not be a single range that represents what it produces.
I know it has one bug (that I've not bothered chasing):
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2009-12/msg00558.html
> I don't know where it lives, but I believe Nicholas wrote it. It's
> obviously based on git log and appears to use a date range, so it
> seems that if you want full git log output, you could just use git log
> --since and give it the same date as appears in the e-mail message.
Yet another option I wasn't aware of. However, that won't quite work the same,
as (if I RTFM correctly) it won't show commits made before $date but only
pushed.
> But it sounds like what you really want is all the commits since the
> last time perldelta was updated. So something like:
>
> % git log -1 --oneline -- pod/perl5114delta.pod
> 7e2aafc remove remaining boilerplate from perl5114delta
> % git log 7e2aafc..
> <snip>
>
> might do the trick, no? For extra credit, write something that
That would be risky, because if anyone commits a typo change to perldelta,
then it "resets" the marker.
Nicholas Clark
> On Sat, Jan 23, 2010 at 8:04 AM, Ricardo Signes
> <perl.p5p@rjbs.manxome.org> wrote:
> > * Perl 5 commit summary <nick@ccl4.org> [2010-01-22T21:08:19]
> >> Perl 5 commit summary, activity since Wednesday
> >>
> >> Current branch blead
> >> 21 commits. 6 unique authors. 5 unique committers.
> >> 97 files changed, 1984 insertions(+), 1487 deletions(-)
> >> Net code removal: Nicholas Clark (676 lines)
> >> Thanks, applied: David Golden (1)
> >> Snapshot: http://perl5.git.perl.org/perl.git/snapshot/fe61459e95657c43.tar.gz
> >
> > Is the script that generates this available for mucking about? If not, what
> > I'd really like is to have it provide a git range like deaf0a1..fb0a1b2 so that
> > I could easily run "git log RANGE" and update perldelta based on the full text
> > of the commits, rather than "have to" click all the links below.
> >
> > I realize there are middle grounds, but that would be convenient. This
> > message can serve both as a reminder to update perldelta /and/ a quick note of
> > which changes require review.
It's on dromedary in /home/nicholas/Perl/summary
However, it's not directly generating any ranges, as its comparing the state
of `git show-ref` before and after `git fetch`, against a private repository
clone. There may not be a single range that represents what it produces.
I know it has one bug (that I've not bothered chasing):
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2009-12/msg00558.html
> I don't know where it lives, but I believe Nicholas wrote it. It's
> obviously based on git log and appears to use a date range, so it
> seems that if you want full git log output, you could just use git log
> --since and give it the same date as appears in the e-mail message.
Yet another option I wasn't aware of. However, that won't quite work the same,
as (if I RTFM correctly) it won't show commits made before $date but only
pushed.
> But it sounds like what you really want is all the commits since the
> last time perldelta was updated. So something like:
>
> % git log -1 --oneline -- pod/perl5114delta.pod
> 7e2aafc remove remaining boilerplate from perl5114delta
> % git log 7e2aafc..
> <snip>
>
> might do the trick, no? For extra credit, write something that
That would be risky, because if anyone commits a typo change to perldelta,
then it "resets" the marker.
Nicholas Clark