Cyclone-Team/gramps
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

* src/data/tips.xml.in: Update bug tracker address.

Browse Source 
svn: r7453
This commit is contained in:
Alex Roitman 2006-10-27 18:51:12 +00:00
parent eddaaa9bc3
commit 2cc0b94a43
2 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
gramps2/ChangeLog
View File

@ -1,4 +1,5 @@
2006-10-27 Alex Roitman <shura@gramps-project.org> 2006-10-27 Alex Roitman <shura@gramps-project.org>
* src/data/tips.xml.in: Update bug tracker address.
* src/const.py.in: Put gettext import back. * src/const.py.in: Put gettext import back.
2006-10-26 Alex Roitman <shura@gramps-project.org> 2006-10-26 Alex Roitman <shura@gramps-project.org>

10
gramps2/src/data/tips.xml.in
View File

@ -221,9 +221,9 @@ Check it out.
<b>Improving GRAMPS</b>: Users are encouraged to request enhancements to <b>Improving GRAMPS</b>: Users are encouraged to request enhancements to
GRAMPS. GRAMPS.
Requesting an enhancement can be done either through the gramps-users or Requesting an enhancement can be done either through the gramps-users or
gramps-devel mailing lists, or by creating a Request for Enhancement (RFE) at gramps-devel mailing lists, or by creating a Feature Request at
http://sourceforge.net/tracker/?group_id=25770&amp;atid=385140 http://bugs.gramps-project.org
Filing an RFE is preferred. Filing a Feature Request is preferred.
</_tip> </_tip>
<_tip number="32"> <_tip number="32">
@ -366,8 +366,8 @@ ready for upload to the World Wide Web.
</_tip> </_tip>
<_tip number="50"> <_tip number="50">
The best way to report a bug in GRAMPS is to use the GRAMPS Bug Tracker The best way to report a bug in GRAMPS is to use the GRAMPS bug tracking
at Sourceforge, http://sourceforge.net/tracker/?group_id=25770&amp;atid=385137 system at http://bugs.gramps-project.org
</_tip> </_tip>
<_tip number="51"> <_tip number="51">