Last modified: 2012-01-14 17:29:15 UTC
Right now associating revisions only goes one way. That's fine in the backend, but in the front-end it'd be nice if it reverse could be shown as well. For example r108869 follows-up r108866. On r108866 it is listed under Follow-up revisions, but there is no link the other way. Of course when the revision id is mentioned in the commit message it can be linked from there, but in particularly long commit messages it'd still be convenient to have them listed and in ascending order. Perhaps rename "Follow-up revisions" section to "References revisions" and show a table for each direction ? (or add another section). Possible issue: Database query may not be indexed the other way around.
We already have "CodeReivision::addReferencesFrom()" and "CodeReivision::addReferencesTo()" As for indexes, we are fine: -- And for our commenting system... -- To specify follow-up relationships... CREATE TABLE /*_*/code_relations ( cf_repo_id int not null, -- -> cr_id cf_from int not null, -- -> cr_id cf_to int not null, primary key (cf_repo_id, cf_from, cf_to) ) /*$wgDBTableOptions*/; CREATE INDEX /*i*/repo_to_from ON /*_*/code_relations (cf_repo_id, cf_to, cf_from); Always filter by the repo, then we can do a query on to or from no issue!
r108907, r108911, r108912
Are you wanting the ability to add newer revisions which follow it up? I guess it'd be useful for adding revisions in from comments etc...
Done. The only thing that might need message tweaks
