[RFC] proposed user doc for nested trees
Ben Finney
ben+bazaar at benfinney.id.au
Thu May 7 23:17:19 BST 2009
Vincent, your quoting style is very annoying to read; please use the
conventional “> ” quote leader without the huge indentation.
As a native English speaker, I disagree with some of the edit
suggestions you make here:
Vincent Ladeuil <v.ladeuil+lp at free.fr> writes:
> >>>>> "Ian" == Ian Clatworthy <ian.clatworthy at internode.on.net> writes:
> Ian> +Bazaar has good support for building and managing external libraries
>
> s/has good support for/supports/. Support is a boolean.
No, it's not (in English, anyway). Support is analogue, and can be rated
good or bad.
> Ian> +and subprojects via a feature known as *nested items*.
>
> s/a feature known//
I find Ian's phrasing to be clearer; it explicitly introduces a new
concept for the reader.
> Ian> +Undoing nested branch changes
> Ian> +-----------------------------
> Ian> +
> Ian> +While committing in a containing branch will commit in nested branches
>
> s/will/, bzr will/
Ian is using the noun role of “committing”; i.e. “While (the act of)
committing in a containing branch will …”.
Perhaps this would be clearer as: “While ‘bzr commit’ in a containing
branch will …”
--
\ “If you have the facts on your side, pound the facts. If you |
`\ have the law on your side, pound the law. If you have neither |
_o__) on your side, pound the table.” —anonymous |
Ben Finney
More information about the bazaar
mailing list