Re: [PATCH] HACKING GUIDE: update and relocate advice on how to write log message for branches.

Thanks for the patch, Gabriela. If you make a common change throughout
your patch, then you have my +1 for commit.

Some of your (patched/new) links look like this:

<a href="...">
LINK TEXT</a>

The whitespace between the > and LINK will appear significant. On a
browser, it might end up looking like:

_LINK

You can patch it in one of (at least) two ways: pull LINK up to the
prior line, or put the newline before the >, pulling the close bracket
down to the next line.

Cheers,
-g

On Thu, Jun 13, 2013 at 3:02 PM, Gabriela Gibson
<gabriela.gibson_at_gmail.com> wrote:
> [[[
>
> Rework branch and log message documentation. Tidy HTML.
>
> * community-guide/conventions.part.html
>
> (log-messages): Rework relocated branch log message documentation
> moved from community-guide/general.part.html#lightweight-branches.
> Remove mention of 'CIA' and substitute with ASFBot and update
> link. Adjust paragraph containing link to 'partial-commit-access'
> to columns limit.
>
> * community-guide/general.part.html
>
> (branch-creation-and-management): Add link to log message section.
>
> (lightweight-branches): Relocate documentation pertaining to log
> messages to community-guide/conventions.part.html#log-messages.
>
> ]]]
>
Received on 2013-06-14 01:15:34 CEST