Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
preprocessor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Dynare
preprocessor
Commits
63ed1cf3
Verified
Commit
63ed1cf3
authored
5 years ago
by
Houtan Bastani
Browse files
Options
Downloads
Patches
Plain Diff
update license dates
(cherry picked from commit
ac3eadc6
)
parent
5029345b
Branches
Branches containing commit
No related tags found
No related merge requests found
Pipeline
#2812
passed
5 years ago
Stage: build
Stage: prepare
Changes
1
Pipelines
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
license.txt
+2
-2
2 additions, 2 deletions
license.txt
with
2 additions
and
2 deletions
license.txt
+
2
−
2
View file @
63ed1cf3
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: Dynare-preprocessor
Upstream-Contact: Dynare Team, whose members in 20
19
are:
Upstream-Contact: Dynare Team, whose members in 20
20
are:
Stéphane Adjemian <stephane.adjemian@univ-lemans.fr>
Houtan Bastani <houtan@dynare.org>
Michel Juillard <michel.juillard@mjui.fr>
...
...
@@ -13,7 +13,7 @@ Upstream-Contact: Dynare Team, whose members in 2019 are:
Source: https://www.dynare.org
Files: *
Copyright: 1996-20
19
Dynare Team
Copyright: 1996-20
20
Dynare Team
License: GPL-3+
Files: m4/ax_boost_base.m4
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment