-
Notifications
You must be signed in to change notification settings - Fork 3
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
Recognise rsync: protocol #37
Comments
Will be added in julianhoersch@b8d902d |
Can I suggest the best way to proceed is to create a topic branch in your own repository (e.g. add-rsync) and then create a pull request on the COMCIFS repository? That will avoid omnibus commits which might be held up by a single problem in a small part. |
Thanks for the suggestions! :) I've created new branches and also the respective pull requests - hope that's how you suggested to proceed. |
Yes, that's perfect.
…On Fri, 3 Feb 2023 at 20:32, Julian Hörsch ***@***.***> wrote:
Thanks for the suggestions! :) I've created new branches and also the
respective pull requests - hope that's how you suggested to proceed.
—
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF2GPWQE5SNBWAPJXVZYK3WVTGDJANCNFSM6AAAAAAUOMG5BE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148
|
The
rsync:
protocol used by SBGrid acts the same as thefile:
protocol in that the per-frame URIs are formed simply by appending the frame file name to the URI.The text was updated successfully, but these errors were encountered: