Hmm, for some reason some of these posts are not showing up in my mail box
until hours later.
On Sun, Feb 17, 2013 at 1:16 AM, Staffan Tylen <[email protected]>wrote:
>
> Someone with the available cycles should jump on Mark's offer of a
>> fast-track to Committer status, and pick this up.
>>
>>
> I don't know what this implies really but having started the avalange I
> feel I need to do something to stop it. I've therefore downloaded the whole
> ooRexx documentation trunk and started to attack the ooDialog material. I
> hope to have that finished within a day or two. What to do with it
> afterwards I'm not sure about, as I've never uploaded anything back.
>
Staffan,
You will not be able to upload anything until you are made a committer.
What you need to do is prepare a patch, or patches, and open up a Patches
tracker item.
https://sourceforge.net/p/oorexx/patches/
I think the best approach would probably be to get all your changes done in
your local working copy, and then just prepare a patch for one .xml file.
Open up a ticket and attach the patch to it, and I'll check that it
applies okay. Maybe open up several tickets for several files.
Then if things go well, you could either prepare a single patch for
everything else, or finish up by preparing a patch for each remaining file.
I'm assuming you have used svn to check out a working copy. TortoiseSVN
seems to be very good at creating a patch file. But, if you are using a
command line svn you can use that to create the patch.
To use a command line svn, follow this procedure. The procedure would be
the same using TortoiseSVN, but you would need to use the menu commands
obviously. Assuming your working copy as some changes from what is in the
repository:
1.) Be sure you do an update first to sync the working copy with the
repository. Failing to do this will lead to problems. Notice that I am
doing this from this repository URL
svn.code.sf.net/p/oorexx/code-0/docs/trunk
which I have checked out into a local directory name docs, bypassing the
whole 'trunk' thing in my local copy:
C:\work.ooRexx\wc\docs>svn update
Updating '.':
At revision 9002.
2.) Use the status command to see what files have differences from the
repository:
C:\work.ooRexx\wc\docs>svn status -q
M oodialog\en-US\userInput.xml
3.) You will have a number of files listed most likely. Create a patch for
just one of them to get started. You use the diff command to create the
patch and redirect the output to a file. You can name the file anything
you like, but it is common to use an extension of 'patch' and some file
name that indicates what the patch is for.
C:\work.ooRexx\wc\docs>svn diff oodialog\en-US\userInput.xml >
userInput.patch
4.) Open the patch file in an editor just to see what it looks like. The
patch file I just did starts out like this:
Index: oodialog/en-US/userInput.xml
===================================================================
--- oodialog/en-US/userInput.xml (revision 9002)
+++ oodialog/en-US/userInput.xml (working copy)
@@ -2737,9 +2737,9 @@
<indexterm><primary>PropertyDialog
class</primary><secondary>absoluteWidth</secondary></indexterm>
<programlisting>
<![CDATA[
->>--absoluteWidth-----------------------------------------------------><
+>>--absoluteWidth--------------------------------><
->>--absoluteWidth = pixels-------------------------------------------><
+>>--absoluteWidth = trueOrFalse------------------><
]]>
</programlisting>
@@ -2792,22 +2792,32 @@
<indexterm><primary>PropertyDialog
class</primary><secondary>canCancel</secondary></indexterm>
<programlisting>
<![CDATA[
->>--canCancel-----------------------------------------------------><
+>>--canCancel------------------------------------><
->>--canCancel = varName-------------------------------------------><
+>>--canCancel = trueOrFalse----------------------><
]]>
</programlisting>
and goes on some.
5.) Open up a Patches ticket on SourceForge, briefly describe what the
patch is for, and attach the patch file to the ticket
As I said, it is probably best to get all your changes done, but just open
a first patches ticket for one file. If there is some problem with that
first one we can work out what is wrong. Once that is straightened out,
you can do all the rest.
If it looks like everything is going well and you will be able to supply
the patches for all of the ooDialog doc, I'll switch any new stuff I'm
adding to the new format.
--
Mark Miesfeld
------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Oorexx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-users
