svnbook-dev Digest, Vol 147, Issue 2

Chinh Do chinh.d.v at gmail.com
Mon Dec 4 18:20:59 CST 2017


Ok, thanks for the clarification.

On Dec 4, 2017 9:03 PM, "C. Michael Pilato" <cmpilato at red-bean.com> wrote:

> Chinh Do, I do not update the translation folders to track changes in the
> English version.  Historically, different translators have taken different
> approaches to managing the work they do, so I try to stay out of the way as
> much as possible.  Generally, I will only modify a translation if there's
> an obvious syntactical error (a missing XML tag, or something) that's
> causing build breakage.
>
> On Sun, Dec 3, 2017 at 9:07 PM, Chinh Do <chinh.d.v at gmail.com> wrote:
>
>> Hi Mike,
>>
>> For changes like this, did you manage to update also the folders (for
>> each language) in branches/1.8 or do we (translators) have to track the
>> changes and copy the new contents ourselves?
>>
>> Thanks,
>> Chinh
>>
>>              </indexterm>
>>              <para>Use this to schedule the file, directory, or
>>                symbolic link <filename>FOO</filename> to be deleted
>> -              from the repository.  If <filename>FOO</filename> is a
>> -              file or link, it is immediately deleted from your
>> -              working copy.  If <filename>FOO</filename> is a
>> -              directory, it is not deleted, but Subversion schedules
>> -              it for deletion.  When you commit your
>> -              changes, <filename>FOO</filename> will be entirely
>> -              removed from your working copy and the
>> -              repository.<footnote><para>Of course, nothing is ever
>> -              totally deleted from the repository—just from
>> -              its <literal>HEAD</literal> revision.  You may continue
>> -              to access the deleted item in previous revisions.
>> -              Should you desire to resurrect the item so that it is
>> -              again present in <literal>HEAD</literal>, see
>> +              from the repository.  <filename>FOO</filename> is
>> +              immediately deleted from your working copy.
>> +              (Of course, nothing is ever totally deleted from the
>> +              repository—just from its <literal>HEAD</literal>
>> revision.
>> +              You may continue to access the deleted item in previous
>> +              revisions).
>> +              <footnote><para>Should you desire to resurrect the item
>> +              so that it is again present in <literal>HEAD</literal>, see
>>                <xref linkend="svn.branchmerge.basicmerging.resurrect"
>>                />.</para></footnote></para>
>>            </listitem>
>>
>> On Sun, Dec 3, 2017 at 1:00 AM, <svnbook-dev-request at red-bean.com> wrote:
>>
>>> Send svnbook-dev mailing list submissions to
>>>         svnbook-dev at red-bean.com
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>         http://www.red-bean.com/mailman/listinfo/svnbook-dev
>>> or, via email, send a message with subject or body 'help' to
>>>         svnbook-dev-request at red-bean.com
>>>
>>> You can reach the person managing the list at
>>>         svnbook-dev-owner at red-bean.com
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of svnbook-dev digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>>    1. [svnbook] r5514 committed -
>>>       trunk/en/book/ch02-basic-usage.xml
>>>       (richardcavell at users.sourceforge.net)
>>>    2. Re: [svnbook] r5514 committed -
>>>       trunk/en/book/ch02-basic-usage.xml (C. Michael Pilato)
>>>    3. Re: [svnbook] r5514 committed -
>>>       trunk/en/book/ch02-basic-usage.xml (Richard Cavell)
>>>
>>>
>>> ----------------------------------------------------------------------
>>>
>>> Message: 1
>>> Date: Fri, 01 Dec 2017 23:30:58 +0000
>>> From: richardcavell at users.sourceforge.net
>>> To: svnbook-dev at red-bean.com
>>> Subject: [svnbook] r5514 committed -
>>>         trunk/en/book/ch02-basic-usage.xml
>>> Message-ID:
>>>         <1512171058.495858.17947 at sfp-scm-6.v30.ch3.sourceforge.com>
>>> Content-Type: text/plain; charset=UTF-8
>>>
>>> Revision: 5514
>>>           http://sourceforge.net/p/svnbook/source/5514
>>> Author:   richardcavell
>>> Date:     2017-12-01 23:30:58 +0000 (Fri, 01 Dec 2017)
>>> Log Message:
>>> -----------
>>> Modify chapter 2's description of svn delete FOO
>>>
>>> In fact, svn delete *does* immediately remove directories, as well as
>>> files
>>> and symlinks. This is true on svn 1.8 and 1.9. The behaviour described
>>> by the
>>> previous version of the book applied to previous versions of svn.
>>>
>>> Discussed on #svn on Freenode on 1 December 2017.
>>>
>>> Modified Paths:
>>> --------------
>>>     trunk/en/book/ch02-basic-usage.xml
>>>
>>> Modified: trunk/en/book/ch02-basic-usage.xml
>>> ===================================================================
>>> --- trunk/en/book/ch02-basic-usage.xml  2017-12-01 14:32:37 UTC (rev
>>> 5513)
>>> +++ trunk/en/book/ch02-basic-usage.xml  2017-12-01 23:30:58 UTC (rev
>>> 5514)
>>> @@ -703,19 +703,14 @@
>>>              </indexterm>
>>>              <para>Use this to schedule the file, directory, or
>>>                symbolic link <filename>FOO</filename> to be deleted
>>> -              from the repository.  If <filename>FOO</filename> is a
>>> -              file or link, it is immediately deleted from your
>>> -              working copy.  If <filename>FOO</filename> is a
>>> -              directory, it is not deleted, but Subversion schedules
>>> -              it for deletion.  When you commit your
>>> -              changes, <filename>FOO</filename> will be entirely
>>> -              removed from your working copy and the
>>> -              repository.<footnote><para>Of course, nothing is ever
>>> -              totally deleted from the repository—just from
>>> -              its <literal>HEAD</literal> revision.  You may continue
>>> -              to access the deleted item in previous revisions.
>>> -              Should you desire to resurrect the item so that it is
>>> -              again present in <literal>HEAD</literal>, see
>>> +              from the repository.  <filename>FOO</filename> is
>>> +              immediately deleted from your working copy.
>>> +              (Of course, nothing is ever totally deleted from the
>>> +              repository—just from its <literal>HEAD</literal>
>>> revision.
>>> +              You may continue to access the deleted item in previous
>>> +              revisions).
>>> +              <footnote><para>Should you desire to resurrect the item
>>> +              so that it is again present in <literal>HEAD</literal>,
>>> see
>>>                <xref linkend="svn.branchmerge.basicmerging.resurrect"
>>>                />.</para></footnote></para>
>>>            </listitem>
>>>
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 2
>>> Date: Fri, 1 Dec 2017 22:59:57 -0500
>>> From: "C. Michael Pilato" <cmpilato at gmail.com>
>>> To: richardcavell at users.sourceforge.net
>>> Cc: svnbook-dev at red-bean.com
>>> Subject: Re: [svnbook] r5514 committed -
>>>         trunk/en/book/ch02-basic-usage.xml
>>> Message-ID:
>>>         <CABUQHU5nyGYW-OCnn1XWVBg9F-jFvZ6XZR6DgB6umghtbbxamQ at mail.gm
>>> ail.com>
>>> Content-Type: text/plain; charset="utf-8"
>>>
>>> I can't see the context right now, but is it worth noting here that in
>>> the
>>> directory case, the directory won't be removed if there are unversioned
>>> items within it?
>>>
>>> --
>>> Sent via mobile. Please excuse brevity.
>>>
>>> On Dec 1, 2017 6:57 PM, <richardcavell at users.sourceforge.net> wrote:
>>>
>>> > Revision: 5514
>>> >           http://sourceforge.net/p/svnbook/source/5514
>>> > Author:   richardcavell
>>> > Date:     2017-12-01 23:30:58 +0000 (Fri, 01 Dec 2017)
>>> > Log Message:
>>> > -----------
>>> > Modify chapter 2's description of svn delete FOO
>>> >
>>> > In fact, svn delete *does* immediately remove directories, as well as
>>> files
>>> > and symlinks. This is true on svn 1.8 and 1.9. The behaviour described
>>> by
>>> > the
>>> > previous version of the book applied to previous versions of svn.
>>> >
>>> > Discussed on #svn on Freenode on 1 December 2017.
>>> >
>>> > Modified Paths:
>>> > --------------
>>> >     trunk/en/book/ch02-basic-usage.xml
>>> >
>>> > Modified: trunk/en/book/ch02-basic-usage.xml
>>> > ===================================================================
>>> > --- trunk/en/book/ch02-basic-usage.xml  2017-12-01 14:32:37 UTC (rev
>>> 5513)
>>> > +++ trunk/en/book/ch02-basic-usage.xml  2017-12-01 23:30:58 UTC (rev
>>> 5514)
>>> > @@ -703,19 +703,14 @@
>>> >              </indexterm>
>>> >              <para>Use this to schedule the file, directory, or
>>> >                symbolic link <filename>FOO</filename> to be deleted
>>> > -              from the repository.  If <filename>FOO</filename> is a
>>> > -              file or link, it is immediately deleted from your
>>> > -              working copy.  If <filename>FOO</filename> is a
>>> > -              directory, it is not deleted, but Subversion schedules
>>> > -              it for deletion.  When you commit your
>>> > -              changes, <filename>FOO</filename> will be entirely
>>> > -              removed from your working copy and the
>>> > -              repository.<footnote><para>Of course, nothing is ever
>>> > -              totally deleted from the repository—just from
>>> > -              its <literal>HEAD</literal> revision.  You may continue
>>> > -              to access the deleted item in previous revisions.
>>> > -              Should you desire to resurrect the item so that it is
>>> > -              again present in <literal>HEAD</literal>, see
>>> > +              from the repository.  <filename>FOO</filename> is
>>> > +              immediately deleted from your working copy.
>>> > +              (Of course, nothing is ever totally deleted from the
>>> > +              repository—just from its <literal>HEAD</literal>
>>> > revision.
>>> > +              You may continue to access the deleted item in previous
>>> > +              revisions).
>>> > +              <footnote><para>Should you desire to resurrect the item
>>> > +              so that it is again present in <literal>HEAD</literal>,
>>> see
>>> >                <xref linkend="svn.branchmerge.basicmerging.resurrect"
>>> >                />.</para></footnote></para>
>>> >            </listitem>
>>> >
>>> >
>>> > _______________________________________________
>>> > svnbook-dev mailing list
>>> > svnbook-dev at red-bean.com
>>> > http://www.red-bean.com/mailman/listinfo/svnbook-dev
>>> -------------- next part --------------
>>> An HTML attachment was scrubbed...
>>> URL: <http://www.red-bean.com/pipermail/svnbook-dev/attachments/2
>>> 0171201/5e61fb56/attachment-0001.html>
>>>
>>> ------------------------------
>>>
>>> Message: 3
>>> Date: Sat, 2 Dec 2017 16:59:27 +0100
>>> From: "Richard Cavell" <richardcavell at mail.com>
>>> To: cmpilato at red-bean.com
>>> Cc: svnbook-dev at red-bean.com
>>> Subject: Re: [svnbook] r5514 committed -
>>>         trunk/en/book/ch02-basic-usage.xml
>>> Message-ID:
>>>         <trinity-3bef35db-5607-4365-afe2-c99e8a5f2d56-1512230367358@
>>> 3c-app-mailcom-lxa07>
>>>
>>> Content-Type: text/plain; charset="utf-8"
>>>
>>> An HTML attachment was scrubbed...
>>> URL: <http://www.red-bean.com/pipermail/svnbook-dev/attachments/2
>>> 0171202/00442817/attachment-0001.html>
>>>
>>> ------------------------------
>>>
>>> Subject: Digest Footer
>>>
>>> _______________________________________________
>>> svnbook-dev mailing list
>>> svnbook-dev at red-bean.com
>>> http://www.red-bean.com/mailman/listinfo/svnbook-dev
>>>
>>> ------------------------------
>>>
>>> End of svnbook-dev Digest, Vol 147, Issue 2
>>> *******************************************
>>>
>>
>>
>> _______________________________________________
>> svnbook-dev mailing list
>> svnbook-dev at red-bean.com
>> http://www.red-bean.com/mailman/listinfo/svnbook-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.red-bean.com/pipermail/svnbook-dev/attachments/20171205/51e02306/attachment-0001.html>


More information about the svnbook-dev mailing list