Yep, that's pretty much it. I like to include the revision number information in the tracker update (when I remember that is :-))
Rick On Thu, Aug 21, 2008 at 4:53 PM, David Ruggles <[EMAIL PROTECTED]> wrote: > I've been way out of the loop. > > I would like to practice committing a change by fixing a small error I found > in the documentation. Before I continue I would like to double check the > correct procedure. > > Should I: > > Create a tracker in Documentation > Commit the change > Update the tracker? > > Thanks, > > David Ruggles > CCNA MCSE (NT) CNA A+ > Network Engineer Safe Data, Inc. > (910) 285-7200 [EMAIL PROTECTED] > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
