[fdo-dev] Empty subversion logs
Romica.Dascalescu at autodesk.com
Fri Sep 8 17:18:51 EDT 2006
You can not drop some changes in the same time if the changes are in
E.g.: if you modify a file from fdocore and one from SHP all these files
are part of the change, but you can not drop them in only one step.
You must do two drops first for fdocore and second from shp. Why should
we put two descriptions if these files are for the same fix (artifact)?
When you drop something in addition you will put a description.
See https://fdo.osgeo.org/servlets/Scarab?id=FDO159 with my last drop.
From: Mateusz Loskot [mailto:mateusz at loskot.net]
Sent: Friday, September 08, 2006 5:11 PM
To: dev at fdo.osgeo.org
Subject: [fdo-dev] Empty subversion logs
Could you explain me how to interpret svn logs and why all svn
logs are empty and only include artifact number?
Here are my detailed questions:
1. Today I run svn update on my FDORDBMS sandbox
and many files have been updated/deleted, with FDO159 artifact in logs.
So, I open the FDO159 artifact in project tracker:
and see there is a description including what was removed/updated, etc.
Is my interpretation correct and this artifact
replaces a traditional svn log message?
Does it mean I don't have to provide detailed logs messages in
PostGIS FDO provider and only put "FDO118" into all messages?
2. Why after commit the artifact is still marked as "New"?
3. Is my assumption correct that there may be more than one commits
for single artifact?
For example, regarding artifact FDO133 there were 5 commits
separated in time (History tab):
If I'm correct, it mean that a single fix or feature is scattered
between various revisions, right?
I'm not sure I understand the FDO policies, so I'd be thankful
for some explanation.
To unsubscribe, e-mail: dev-unsubscribe at fdo.osgeo.org
For additional commands, e-mail: dev-help at fdo.osgeo.org
More information about the Fdo-internals