accountmanagementengineRoot/
| File | Age | Message | Size | |
|---|---|---|---|---|
| .. | ||||
 |
||||
|
||||
 |
Loic d'Anterroches: Added an exception when the scm command fails. | |||
|
Thomas Keller: Introduce a more subtle concept of validity when it comes to revision indentifiers in IDF - the SCM function isValidRevision has been replaced by a validateRevision() method which returns one of three states, valid, invalid or ambiguous. The source view can then act accordingly and display disambiguate view for the latter, so the user can select for which revision he actually wants to execute the requested action. Also, invalid revisions now lead to another separate view, telling the user that it is invalid / does not exist and pointing him optionally to the help page where he can read further how to access his repository to push the first changes into. (partially resolves issue 525) | |||
|
Thomas Keller: Introduce a more subtle concept of validity when it comes to revision indentifiers in IDF - the SCM function isValidRevision has been replaced by a validateRevision() method which returns one of three states, valid, invalid or ambiguous. The source view can then act accordingly and display disambiguate view for the latter, so the user can select for which revision he actually wants to execute the requested action. Also, invalid revisions now lead to another separate view, telling the user that it is invalid / does not exist and pointing him optionally to the help page where he can read further how to access his repository to push the first changes into. (partially resolves issue 525) | |||
|
Thomas Keller: IDF_Scm_Monotone::getCommit() separate the first line of a commit from the rest and write the rest in full_message - just like we do it for log and everything else. This is ugly, really ugly, because it assumes something on the format of a commit message, which might not be true at all for some project, but this is something Loic has to decide (see also issue 491 and issue 535) | |||
|
Thomas Keller: Introduce a more subtle concept of validity when it comes to revision indentifiers in IDF - the SCM function isValidRevision has been replaced by a validateRevision() method which returns one of three states, valid, invalid or ambiguous. The source view can then act accordingly and display disambiguate view for the latter, so the user can select for which revision he actually wants to execute the requested action. Also, invalid revisions now lead to another separate view, telling the user that it is invalid / does not exist and pointing him optionally to the help page where he can read further how to access his repository to push the first changes into. (partially resolves issue 525) | |||
Download this version or
git clone git://archive.srchub.org/indefero.git 