wrote:
> We used to do this in the past, and it was determined that most often
> this isn't what is desired.
>
> The complete history is available for any user to look at in more detail
> if they so desire, but in the situations where people commit *a lot*,
> the email became almost useless.
>
> ** Changed in: launchpad-code
> Status: New => Won't Fix
I think there's room to experiment a little more here -- part of the
problem before was that it was like 'log -v' output and the lists of
changed files from trunk merges became overwhelming. But if we just
showed the log messages somehow intelligently grouped by author and with
a limit on the number we showed in the mail, I think it might be better
than what we have today.
wrote:
> We used to do this in the past, and it was determined that most often
> this isn't what is desired.
>
> The complete history is available for any user to look at in more detail
> if they so desire, but in the situations where people commit *a lot*,
> the email became almost useless.
>
> ** Changed in: launchpad-code
> Status: New => Won't Fix
I think there's room to experiment a little more here -- part of the
problem before was that it was like 'log -v' output and the lists of
changed files from trunk merges became overwhelming. But if we just
showed the log messages somehow intelligently grouped by author and with
a limit on the number we showed in the mail, I think it might be better
than what we have today.
Cheers,
mwh