Project

General

Profile

Actions

Defect #6857

open

git references leaking from subproject to project

Defect #6857: git references leaking from subproject to project

Added by Bernhard Furtmueller about 16 years ago. Updated almost 13 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
SCM
Resolution:
Affected version:

Description

Since redmine can't share repositories to subprojects yet we added the repository twice (to project and subproject).

Now trackers which are referenced in the repository get commit messages attached twice. One time from the project's repo and one time from the subproject's repo.

I'd consider this leaking a bug (or a first step to shared repos ;) )


Related issues 8 (5 open — 3 closed)

Related to Redmine - Feature #1657: Subprojects can share their parent project's repositoryNewActions
Related to Redmine - Patch #2144: Patch for main-level repositoryClosedJean-Philippe LangActions
Related to Redmine - Patch #2256: Allow commit messages to refer to issues in project ancestor tree, not just projectClosedActions
Related to Redmine - Feature #3687: Possibility to link all projects to a single SVN repositoryNewActions
Related to Redmine - Patch #9359: invert project <-> repository relationshipNewActions
Has duplicate Redmine - Defect #8225: Revisions that reference issues are duplicated if their repository is listed for a project and its subprojectsNewActions
Has duplicate Redmine - Defect #5126: Associated revision shown multiple timesClosedActions
Has duplicate Redmine - Defect #32191: Duplicate associated revisions when using multiple repositories for a projectNewActions

Updated by Bernhard Furtmueller about 16 years ago Actions #1

I think there were already some attempts getting the root problem (sharing repos) fixed or asked.

Feature #1657 Subprojects can share their parent project's repository
Patch #2144 Patch for main-level repository
Patch #2256 Allow commit messages to refer to issues in project ancestor tree, not just project

Updated by Etienne Massip about 15 years ago Actions #2

  • Target version set to Candidate for next minor release

Yet to be confirmed.

Updated by Mischa The Evil almost 15 years ago Actions #3

Etienne Massip wrote:

Yet to be confirmed.

I haven't looked into this issue deeply but considering r3357 for issue #4674, which was included first in Redmine 0.9.2, it looks like it is logical behavior.

Updated by Fernando Hartmann about 14 years ago Actions #4

+1
This happens to me too

Updated by Ivan Cenov over 13 years ago Actions #5

This happens in 2.2.3.stable too with Subversion repositories.

Updated by Jethro Yu over 13 years ago Actions #6

This happens in 2.2.3.stable too with git repositories.

Updated by Ralph Twele almost 13 years ago Actions #7

I have this happening with 2.3.0. It is not only related to parent-child Projects. I have one repository containing a document describing general development rules. This is included in many Redmine projects. If I commit a change to the document referencing a ticket the new revision will be listed in the ticket multiple times.

Updated by Go MAEDA almost 11 years ago Actions #8

  • Has duplicate Defect #5126: Associated revision shown multiple times added

Updated by Go MAEDA about 7 years ago Actions #9

  • Has duplicate Defect #32191: Duplicate associated revisions when using multiple repositories for a project added
Actions

Also available in: PDF Atom