-
Notifications
You must be signed in to change notification settings - Fork 729
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: mantisbt/mantisbt
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: f087535
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: mantisbt/mantisbt
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: ce6d92d
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 2 commits
- 3 files changed
- 1 contributor
Commits on May 18, 2012
-
Record reporter+submitted date in extended info first revision history
When updating any of the "extended info" fields (Description, Steps To Reproduce, Additional Information), the history of modifications is saved in the mantis_bug_revision_table. When the first change is made since issue creation, an additional, "initial" revision record is created to keep track of the original value. Prior to this, the record was saved with incorrect author and timestamp information: current user and date of modification, instead of the bug's reporter and date of submission. Fixes #14272
Configuration menu - View commit details
-
Copy full SHA for d12e5e9 - Browse repository at this point
Copy the full SHA d12e5e9View commit details -
Remove unnecessary use of array_reverse() to display bug revisions
Prior to this commit, in bug_revision_view_page.php the array returned by functions bug_revision_list() and bug_revision_like() was sytematically reversed by calling array_reverse(). Since these 2 functions are not used anywhere else, it is more efficient to modify the SQL so that the functions sort the list as it should be right from the start, thus avoiding the calls to array_reverse(). Note that the ORDER BY clause has been changed from 'timestamp' to 'id', this guarantees correct display order in case the timestamps are equal since by definition the id is a sequential number increased with each revision as it is recorded. Fixes #14273
Configuration menu - View commit details
-
Copy full SHA for ce6d92d - Browse repository at this point
Copy the full SHA ce6d92dView commit details
There are no files selected for viewing