Patch #2144

Patch for main-level repository

Added by Andrea Maleci about 14 years ago. Updated almost 10 years ago.

Status:ClosedStart date:2008-11-07
Priority:NormalDue date:2008-11-07
Assignee:Jean-Philippe Lang% Done:


Category:SCMEstimated time:2.00 hours
Target version:-


Here is a patch for High-level repository, ref to Issue #2120.
Here how it works:

If a changeset refers to an Issue that has not a linked repository, it looks for an upper lever project, to see if there is a repository. If it has, changeset is linked to that Issue;
If a project has no repository linked and is a subproject, it looks for an upper level project. It there is there, it uses that repository so if ypu click on revisin number linked to related Issue, it shows correctly changes made.

Hope this helps,

ParentRepository.0.7.3.patch Magnifier - Patch for changeset (1.43 KB) Andrea Maleci, 2008-11-07 12:53

Related issues

Related to Redmine - Feature #2120: Different views between develop and funcional New 2008-10-31
Related to Redmine - Defect #6857: git references leaking from subproject to project New 2010-11-09
Related to Redmine - Patch #1601: Make second level navigation for all views in repository ... New 2008-07-08


#1 Updated by Jean-Philippe Lang about 14 years ago

  • Target version deleted (0.7.3)

Thanks for the patch.
Target removed because already released.

#2 Updated by Arthaey Angosii almost 14 years ago

Thanks for writing this patch! It successfully closed a subproject's issue from the commit message.

However, it would be nice if the subproject would also display the "Associated Revisions" section.

#3 Updated by Jan Niggemann ( team member) almost 10 years ago

  • Status changed from Resolved to Closed

Closing this, status is resolved since 400 days and more (issue was last updated more than 400 days ago)...

Also available in: Atom PDF