[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: automated computing tasks for lilypond
From: |
Graham Percival |
Subject: |
Re: automated computing tasks for lilypond |
Date: |
Wed, 29 Aug 2012 14:19:54 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Wed, Aug 29, 2012 at 02:09:43PM +0100, James wrote:
> Just an off-the-cuff suggestion. If we had a 'patch-new-doc' and a
> 'patch-new' label would that be useful and tell patchy if it sees the
> former to build doc as well?
I suppose so, although people uploading with git-cl would need to
specify that it was a doc patch... or perhaps git-cl could
recognize if Documentation/ or ly/ or scm/ were modified.
However, I think this is a solution looking for a problem. How
often does a patch fail on staging-merge due to doc issues? If we
have a lot of those, then it may be worth fiddling with
test-patches. But I can't think of many such breakages in the
past six months.
- Graham
Re: automated computing tasks for lilypond, Graham Percival, 2012/08/29
- Re: automated computing tasks for lilypond, James, 2012/08/29
- Re: automated computing tasks for lilypond, John Mandereau, 2012/08/29
- Re: automated computing tasks for lilypond, James, 2012/08/29
- Re: automated computing tasks for lilypond,
Graham Percival <=
- Re: automated computing tasks for lilypond, James, 2012/08/29
- Re: automated computing tasks for lilypond, John Mandereau, 2012/08/29
Re: automated computing tasks for lilypond, John Mandereau, 2012/08/29
Re: automated computing tasks for lilypond, James, 2012/08/29
Re: automated computing tasks for lilypond, John Mandereau, 2012/08/30
Re: automated computing tasks for lilypond, James, 2012/08/30
Re: automated computing tasks for lilypond, John Mandereau, 2012/08/31
Re: automated computing tasks for lilypond, David Kastrup, 2012/08/28
Re: automated computing tasks for lilypond, Janek WarchoĊ, 2012/08/28