Maneage - Tasks: task #15545, Warning/error if changes aren't...
You are not allowed to post comments on this tracker with your current authentication level.
task #15545: Warning/error if changes aren't committed
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Mon 10 Feb 2020 10:42:35 PM UTC | ||
Should Start On: | Mon 10 Feb 2020 12:00:00 AM UTC | Should be Finished on: | Mon 10 Feb 2020 12:00:00 AM UTC |
Category: | Analysis | Priority: | 5 - Normal |
Status: | Postponed | Privacy: | Public |
Assigned to: | None | Percent Complete: | 0% |
Open/Closed: | Open | Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
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 |
---|---|---|---|---|---|
2020-02-10 | makhlaghi | Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-d3ae.
Corresponding source code
Currently if any change isn't committed, the project will just add a `-dirty' suffix to the commit checksum which is printed into the paper at the end of the abstract (this is from the the `--dirty' option that the project passes onto `git describe').
But this is not enough and can easily go unnoticed! To encourage people to commit their changes, a warning should be printed after building the PDF which tells the user that there are uncommitted changes. We can further strengthen this with a configure option (for example `--run-committed'!). When this option is called, if there are uncommitted changes, the project shouldn't build at all.
This task was suggested by Nadia Tonello.