On Wed, 2010-11-17, Stefan Sperling wrote:
> On Wed, Nov 17, 2010 at 12:04:21PM +0000, Julian Foad wrote:
> > I think it would be better if we only issue this warning when the
> > proposed commit does in fact include a copy, otherwise it's going to be
> > too much noise.
> > Thoughts?
> The warning is printed very early in the commit process, way before
> the commit targets are harvested. Printing the warning at a later stage
> is much harder to do, especially in light of backporting the change
> to 1.6.x because that would require API changes (the backport has
> happened in 1.6.13).
> But yes, I agree that it would be better to print the warning only
> if the commit harvester has actually picked up a copy. We could file
> an issue with 1.7.0 milestone for this, and I'll try to take a crack
> at it if I can find the time.
Great, thanks. Issue #3752
about committing copied dir at depth 'empty'". I won't hold you to
working on it, of course.
Received on 2010-11-17 14:47:48 CET