Author: glen                         Date: Wed Apr  2 22:30:56 2008 GMT
Module: SPECS                         Tag: HEAD
---- Log message:
- adapter, add changelog

---- Files affected:
SPECS:
   ditz.spec (1.1 -> 1.2) 

---- Diffs:

================================================================
Index: SPECS/ditz.spec
diff -u SPECS/ditz.spec:1.1 SPECS/ditz.spec:1.2
--- SPECS/ditz.spec:1.1 Wed Apr  2 23:55:09 2008
+++ SPECS/ditz.spec     Thu Apr  3 00:30:51 2008
@@ -4,12 +4,12 @@
 Version:       0.1
 Release:       1
 License:       Ruby
-Source0:       http://rubyforge.org/frs/download.php/34859/ditz-0.1.tgz
+Source0:       
http://rubyforge.org/frs/download.php/34859/%{name}-%{version}.tgz
 # Source0-md5: 1ea135ab10fff82ed240d1cd5fc94f12
 Group:         Development/Tools
 Patch0:                %{name}-nogems.patch
 Patch1:                %{name}-paths.patch
-URL:   http://ditz.rubyforge.org/
+URL:           http://ditz.rubyforge.org/
 BuildRequires: rpmbuild(macros) >= 1.277
 BuildRequires: ruby-modules
 BuildRequires: setup.rb
@@ -18,18 +18,19 @@
 BuildRoot:     %{tmpdir}/%{name}-%{version}-root-%(id -u -n)
 
 %description
-Ditz is a simple, light-weight distributed issue tracker designed to work
-with distributed version control systems like darcs and git. Ditz maintains
-an issue database file on disk, written in a line-based and human-editable
-format. This file is kept under version control, alongside project code.
-Changes in issue state is handled by version control like code change:
-included as part of a commit, merged with changes from other developers,
-conflict-resolved in the standard manner, etc.
-
-Ditz provides a simple, console-based interface for creating and updating
-the issue database file, and some rudimentary HTML generation capabilities
-for producing world-readable status pages. It offers no central public
-method of bug submission.
+Ditz is a simple, light-weight distributed issue tracker designed to
+work with distributed version control systems like darcs and git. Ditz
+maintains an issue database file on disk, written in a line-based and
+human-editable format. This file is kept under version control,
+alongside project code. Changes in issue state is handled by version
+control like code change: included as part of a commit, merged with
+changes from other developers, conflict-resolved in the standard
+manner, etc.
+
+Ditz provides a simple, console-based interface for creating and
+updating the issue database file, and some rudimentary HTML generation
+capabilities for producing world-readable status pages. It offers no
+central public method of bug submission.
 
 %prep
 %setup -q
@@ -61,3 +62,12 @@
 
 %define date   %(echo `LC_ALL="C" date +"%a %b %d %Y"`)
 %changelog
+* %{date} PLD Team <[EMAIL PROTECTED]>
+All persons listed below can be reached at <cvs_login>@pld-linux.org
+
+$Log$
+Revision 1.2  2008-04-02 22:30:51  glen
+- adapter, add changelog
+
+Revision 1.1  2008-04-02 21:55:09  aredridel
+- added
================================================================

---- CVS-web:
    
http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/SPECS/ditz.spec?r1=1.1&r2=1.2&f=u

_______________________________________________
pld-cvs-commit mailing list
[email protected]
http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit

Reply via email to