Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Separate timestamp from config #31

Open
ArneBachmann opened this issue Jan 18, 2017 · 4 comments
Open

Separate timestamp from config #31

ArneBachmann opened this issue Jan 18, 2017 · 4 comments
Labels
enhancement investigate question
Milestone
V2.0

Comments

@ArneBachmann
Copy link
Owner

It's currently a key feature, but maybe there's a better solution that doesn't change the config itself? E.g. touch or similar?
Would be VCS friendlier.
@ArneBachmann ArneBachmann added this to the V1.0 milestone Jan 18, 2017
@ArneBachmann
Copy link
Owner Author

Could also be kept outside VCS by exclude rule

@ArneBachmann
Copy link
Owner Author

Also related to the problem regarding config contents being reordered due to the missing orderedt default dict.

@ArneBachmann ArneBachmann modified the milestones: V2.0, V1.0 Mar 3, 2017
@ArneBachmann
Copy link
Owner Author

Not sure if still necessary. If the config is under VCS, changes are tracked anyway, one timestamp doesn't hurt (but still could be avoided by relying on mtime). Dict's are ordered by default now, probably even the default dict.

@ArneBachmann ArneBachmann mentioned this issue Jan 28, 2021
Closed
@ArneBachmann
Copy link
Owner Author

Issue #68 is one more reason to use the file system's timestamp instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement investigate question
Projects
None yet
Milestone
V2.0
Development

No branches or pull requests
1 participant
@ArneBachmann