Merge lp:~vila/bzr/mergetool-doc into lp:bzr
| Status: | Merged |
|---|---|
| Approved by: | Martin Packman on 2012-10-10 |
| Approved revision: | 6568 |
| Merged at revision: | 6569 |
| Proposed branch: | lp:~vila/bzr/mergetool-doc |
| Merge into: | lp:bzr |
| Diff against target: |
25 lines (+16/-0) 1 file modified
bzrlib/help_topics/en/configuration.txt (+16/-0) |
| To merge this branch: | bzr merge lp:~vila/bzr/mergetool-doc |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Martin Packman (community) | 2012-09-19 | Approve on 2012-09-19 | |
|
Review via email:
|
|||
Commit Message
Clarify how `mergetool` templates should be used with `bzr config`.
Description of the Change
Basde on an IRC discussion with mgz.
I think that should address
https:/
- 6566. By Vincent Ladeuil on 2012-09-19
-
Tone down ;)
| Vincent Ladeuil (vila) wrote : | # |
Is that better ?
| Martin Packman (gz) wrote : | # |
Typo, 'conflit'. But actually I find the sentence still rather hard to read, let's see if I can help...
"""
Because mergetool and config itself both use curly braces as interpolation markers, trying to display the mergetool line results in the following problem:
...
To avoid this, config can be instructed not to try expanding variables:
...
"""
Something like that? This is user-focused after all, so they shouldn't really care too much about the details.
- 6567. By Vincent Ladeuil on 2012-10-10
-
Don't explain gory details, most users won't care.
- 6568. By Vincent Ladeuil on 2012-10-10
-
Fix formattting.
| Vincent Ladeuil (vila) wrote : | # |
> Typo, 'conflit'. But actually I find the sentence still rather hard to read,
> let's see if I can help...
Thanks ;)
> Something like that? This is user-focused after all, so they shouldn't really
> care too much about the details.
Agreed, done.
| Vincent Ladeuil (vila) wrote : | # |
sent to pqm by email

So, I don't like "the following will (rightly) break", and perhaps we don't want to give the "wrong" version at all, but perhaps it's useful for people doing a search on the error message? So, just tone down the "we write software that's hard to use on purpose" angle and this should be fine.