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.
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
Issue 73 #100
Issue 73 #100
Conversation
0348cf6
to
a6480c1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good overall.
I got help from Globus on how to test this. I added a test case for it. |
3d62bd0
to
7086a36
Compare
I rebased this on main after issue 65 was merged. |
looks good - this passes the tests? are you going to squash to one? or two (code+test)? |
Yes, it passes the tests. I'll squash to one I think. |
Seems good. |
I squashed with no pound. |
yep - i think we're ready for undrafting and some @alanking eyeballs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Let's get one more approval before pounding.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just had one suggestion for a potential improvement. Otherwise, looks good.
I updated the commit message to state "preserve file modification time" instead of "preserve replica". I think my brain was on autopilot when I wrote the original message. |
If the tests pass, let's squash it. |
done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please pound if ready.
Add test for modify time preservation
done |
Opening in draft mode while I figure out how to test this.
Ignore commit for issue 65 as this will be rebased on that once its pull request is finished.