This may seem a chore, but module issues should always be reported in

http://www.crosswire.org/tracker/browse/MOD/

Separate issue for each module, please.

One of the reasons we have a tracker is that our mailing list doesn't act
very well as a "to do" list.

As I see it, the nub of the problem is hidden in the words "just needs
rebuilding from the same OSIS".

Who knows who has the OSIS file from which each module was last built?

And if the person who has the file is incommunicado, we're stumped!

David

 





--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Module-problems-tp4654590p4654600.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Reply via email to