#153 1.12.1. Null Clauses

4.0.0
closed
Mark Miesfeld
Reference (110)
5
2012-08-14
2009-07-16
Craig Harris
No

A clause consisting only of whitespace characterss, comments, or both is a null clause. It is completely ignored.

characterss s/b characters

I installed TortiseSVN, got ...docs/trunk from repository and put in my working copy, found the typo in intro.sgml, made the change, saved intro.sgml and created a patch file. It is attached. This is my first time using TortiseSVN, so update me if this is not the optimal way.

Also, how do I cross referene changes from my hard copy to the appropiate sgml file? Or do you have all the sections to sgml file memorized? <grin>

Craig Harris

Discussion

  • Mark Miesfeld
    Mark Miesfeld
    2009-07-16

    Craig, that is excellent.

    The patch is the right way to do this, and TortiseSVN works very well. So this is the optimal way to do this.

    Now that you are getting the hang of it, I'd wait and do several updates all in one patch. I would recommend doing separate patches for something you think might be "controversial." In other words you could put as many typos in a patch as you want.

    But, then if you have something that is a re-wording where people might not agree with your re-wording, I would put that in a separate patch. It makes it easier to apply patches if the entire patch can be rejected, or the entire patch can be accepted.

    I use grep to find the the right .sgml file.

    C:\work.ooRexx\wc\docs\rexxref>grep "clause consisting only of whitespace characterss" *.sgml
    intro.sgml:<para>A clause consisting only of whitespace characterss, comments, or both is a

    C:\work.ooRexx\wc\docs\rexxref>

    If you supply a patch, you don't need to specify what section it is in to us.

     
  • Craig Harris
    Craig Harris
    2009-07-17

    I notice that you update /docs/trunks and /docs/branches/4.0.0/trunk with the same change. Do you use the same patch file to update both or do you need to create a new patch? Would it help if I attached two patch files, one for each leg?

    Craig Harris

     
  • Mark Miesfeld
    Mark Miesfeld
    2009-07-17

    Just one patch is fine.

    I use a subversion feature that merges the change in the branch into trunk. It is no extra work to do it.

     


Anonymous


Cancel   Add attachments