Maneage - Tasks: task #15363, Better solution to restoring file...
You are not allowed to post comments on this tracker with your current authentication level.
task #15363: Better solution to restoring file dates after Git checkout
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Sat 10 Aug 2019 07:19:01 PM UTC | ||
Should Start On: | Fri 09 Aug 2019 11:00:00 PM UTC | Should be Finished on: | Fri 09 Aug 2019 11:00:00 PM UTC |
Category: | Analysis | Priority: | 6 |
Status: | Postponed | Privacy: | Public |
Assigned to: | None | Percent Complete: | 0% |
Open/Closed: | Open | Effort: | 0.00 |
Sat 17 Aug 2019 07:55:28 PM UTC, comment #1: |
Mohammad Akhlaghi <makhlaghi> |
Sat 10 Aug 2019 07:19:01 PM UTC, original submission:
One major problem with Git is that it doesn't keep the file meta data after a checkout (in particular the date). Git just copies a new file during checkout, so all files that have changed between branches get the current time stamp.
|
Mohammad Akhlaghi <makhlaghi> |
No files currently attached
Depends on the following items: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2022-09-13 | boud | Dependencies | - | task #15942 is dependent |
Powered by Savane 3.13-4448.
Corresponding source code
I just noticed that this doesn't just apply to configuration files. Within a project, we will often set programming sources (in C, Python, or Bash) as prerequisites of steps also. This is commonly done so if anything changes in a script/source, the step that depends on them is re-run.
Therefore the modified solution should work on all the file in directories under `reproduce/analysis' except for `reproduce/analysis/make'.