Login | Register
My pages Projects Community openCollabNet

Discussions > cvs > CVS update: /svnutils/trunk/

svnutils
Discussion topic

Back to topic list

CVS update: /svnutils/trunk/

Author sunny256
Full name Øyvind A. Holm
Date 2004-09-12 15:47:07 PDT
Message User: sunny256
Date: 04/09/12 15:47:07

Modified:
 /svnutils/trunk/
  README.txt

Log:
 r49 | sunny256 | 2004-09-11 17:51:13 +0000 | 4 lines
 
 * /trunk/README.txt
   New look (indented the text) and added a section about contributing to
   the project.

File Changes:

Directory: /svnutils/trunk/
===========================

File [changed]: README.txt
Url: http://svnutils.tigr​is.org/source/browse​/svnutils/trunk/READ​ME.txt?r1=1.1&r2​=1.2
Delta lines: +54 -38
---------------------
--- README.txt 12 Sep 2004 22:41:17 -0000 1.1
+++ README.txt 12 Sep 2004 22:47:07 -0000 1.2
@@ -5,49 +5,65 @@
 
 WHAT IS THIS?
 
-A collection of scripts, libraries and tips for use with the Subversion
-version control system — <http://subversion.ti​gris.org>.
+ A collection of scripts, libraries and tips for use with the
+ Subversion version control system — <http://subversion.ti​gris.org>.
 
-There are some tasks that are repeated several times a day, things like
-examining svn logs and possibly change the wording, checking for updates
-in specific ways, synchronising repositories, etc… Many of us end up
-creating small scripts or aliases for easening those tedious tasks and
-they end up living in ~/bin/ without anyone else getting the use of it.
-
-This project is dedicated to those helpful little scripts or possibly
-larger programs designed for complex and heavy Subversion jobs. No
-special rules about what can be included here, except for two things:
-
- 1. It must be Free Software. No proprietary or closed software can be
- included. It must qualify to the guidelines defined by the Free
- Software Foundation (URL coming later) and preferably be
+ There are some tasks that are repeated several times a day, things
+ like examining svn logs and possibly change the wording, checking for
+ updates in specific ways, synchronising repositories, etc… Many of us
+ end up creating small scripts or aliases for easening those tedious
+ tasks and they end up living in ~/bin/ without anyone else getting the
+ use of it.
+
+ This project is dedicated to those helpful little scripts or possibly
+ larger programs designed for complex and heavy Subversion jobs. No
+ special rules about what can be included here, except for two things:
+
+ 1. It must be Free Software. No proprietary or closed software can
+ be included. It must qualify to the guidelines defined by the
+ Free Software Foundation (URL coming later) and preferably be
      GPL-compatible.
   2. To avoid forking and confusion about where to get the newest
- version of a program, it should not have an official download page
- on the Internet. An exception to this is if the author says it OK
- to import the parts or everything of it into the project.
+ version of a program, it should not have an official download
+ page on the Internet. An exception to this is if the author says
+ it OK to import the parts or everything of it into the project.
 
-A list of the included programs and scripts can be found in the CONTENTS
-file.
+ A list of the included programs and scripts can be found in the
+ CONTENTS file.
 
 DIRECTORY STRUCTURE
 
-If you checked this source out from Subversion, this is the layout of
-the repository:
+ If you checked this source out from Subversion, this is the layout of
+ the repository:
 
-/trunk/
- This is where the development happens. Download this if you want the
- newest versions of everything.
-/trunk/src/
- Newest version of the sources
-/trunk/unfinished
+ /trunk/
+ This is where the development happens. Download this if you want
+ the newest versions of everything.
+ /trunk/src/
+ Newest version of the sources.
+ /trunk/unfinished
     Yes, unfinished scripts.
-/branches/
+ /branches/
   Various branches of the projects.
-/tags/
+ /tags/
   Snapshots of possible releases and such.
-/www/
+ /www/
   HTML files on http://svnutils.tigris.org
 
-$Id: README.txt 48 2004-09-11 17:17:19Z sunny256 $
+CONTRIBUTING TO THE PROJECT
+
+ First of all, ensure that all parts of the program is free so it can
+ be incorporated into the project. We’re not going to make any fuzz of
+ it, but when choosing a license for the program, please try to keep it
+ GPL-compatible to make it possible to mix and borrow source parts into
+ other utilities in the svnutils project.
+
+ The preferred charset in text and source files is UTF-8. The use of
+ Unicode and extremely non-English characters is widespread, so the use
+ of a uniform character set saves us for the mess with multiple charset
+ encodings. Please make sure that you programs deals correctly with
+ UTF-8 streams, as this makes communication with the Subversion system
+ much easier.
+
+$Id: README.txt 49 2004-09-11 17:51:13Z sunny256 $
 vim: set tw=72 ts=2 sw=2 sts=2 et fo+=wn fo-=2 fenc=UTF-8 :




--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: cvs-unsubscribe@svnu​tils.tigris.org
For additional commands, e-mail: cvs-help at svnutils dot tigris dot org

« Previous message in topic | 1 of 1 | Next message in topic »

Messages

Show all messages in topic

CVS update: /svnutils/trunk/ sunny256 Øyvind A. Holm 2004-09-12 15:47:07 PDT
Messages per page: