<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">After reading the section, I have understand the real meaning of title. Maybe<div class="">it is unnecessary to change it.</div><div class=""><br class=""></div><div class="">Thanks.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 13 Nov 2017, at 9:50 PM, C. Michael Pilato <<a href="mailto:cmpilato@red-bean.com" class="">cmpilato@red-bean.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Well, that section is not actually about blocking of merge tracking, but rather about blocking commits made by clients that don't support merge tracking.<div class=""><br class=""></div><div class="">The original sentiment is probably one best expressed using hyphens (as in, "Blocking Merge-Tracking-Unaware Clients"), but long strings of hyphens are generally frowned upon. I notice that the 1.7 version of the book has this title as simply "Blocking Merge-Unaware Clients", which is an improvement grammatically, but still fails to reflect the scope of what's really happening.<div class=""><br class=""></div><div class="">Maybe we should change the title of that section to reflect the *goal* rather than the specific approach. Perhaps something such as "Preserving Mergeinfo Integrity"?</div><div class=""><br class=""></div><div class="">-- Mike</div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sun, Nov 12, 2017 at 1:36 AM, wuzhouhui <span dir="ltr" class=""><<a href="mailto:wuzhouhui14@mails.ucas.ac.cn" target="_blank" class="">wuzhouhui14@mails.ucas.ac.cn</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm not a English-native speaker, but according to my knowledge learned from<br class="">
school, should we add a preposition between "Tracking" and "Unaware", like<br class="">
"For"?<br class="">
<br class="">
Index: en/book/ch04-branching-and-<wbr class="">merging.xml<br class="">
==============================<wbr class="">==============================<wbr class="">=======<br class="">
diff --git a/trunk/en/book/ch04-<wbr class="">branching-and-merging.xml b/trunk/en/book/ch04-<wbr class="">branching-and-merging.xml<br class="">
--- a/trunk/en/book/ch04-<wbr class="">branching-and-merging.xml (revision 5490)<br class="">
+++ b/trunk/en/book/ch04-<wbr class="">branching-and-merging.xml (working copy)<br class="">
@@ -3178,7 +3178,7 @@ D src/integer.c<br class="">
<br class="">
<!-- ==============================<wbr class="">==============================<wbr class="">=== --><br class="">
<sect2 id="svn.branchmerge.advanced.<wbr class="">pre1.5clients"><br class="">
- <title>Blocking Merge Tracking Unaware Clients</title><br class="">
+ <title>Blocking Merge Tracking For Unaware Clients</title><br class="">
<br class="">
<para>If you've just upgraded your server to Subversion 1.5 or<br class="">
later, there's a risk that pre-1.5 Subversion<br class="">
<br class="">
<br class="">
______________________________<wbr class="">_________________<br class="">
svnbook-dev mailing list<br class="">
<a href="mailto:svnbook-dev@red-bean.com" class="">svnbook-dev@red-bean.com</a><br class="">
<a href="http://www.red-bean.com/mailman/listinfo/svnbook-dev" rel="noreferrer" target="_blank" class="">http://www.red-bean.com/<wbr class="">mailman/listinfo/svnbook-dev</a></blockquote></div><br class=""></div>
_______________________________________________<br class="">svnbook-dev mailing list<br class=""><a href="mailto:svnbook-dev@red-bean.com" class="">svnbook-dev@red-bean.com</a><br class="">http://www.red-bean.com/mailman/listinfo/svnbook-dev</div></blockquote></div><br class=""></div></body></html>