Skip to content

Rename git_transfer_progress to git_indexer_progress#4997

Merged
ethomson merged 5 commits into
masterfrom
ethomson/transfer_progress
Feb 22, 2019
Merged

Rename git_transfer_progress to git_indexer_progress#4997
ethomson merged 5 commits into
masterfrom
ethomson/transfer_progress

Conversation

@ethomson

Copy link
Copy Markdown
Member

While going through the API, I found it strange that object database functions took a "transfer progress" callback. In fact, this is a callback for indexer progress that happened to start life as reporting for transfers.

Rename it as such, updating the internal usages and creating a typedef for the old names for backward compatibility.

@ethomson

Copy link
Copy Markdown
Member Author

Sure, I added a similar change for #4654.

@ethomson ethomson force-pushed the ethomson/transfer_progress branch from 4d8bf32 to da3528b Compare February 21, 2019 11:58

@pks-t pks-t left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for breaking your PR 🙄

The name `git_transfer_progress` does not reflect its true purpose.

It suggests that it's progress for a non-existence `git_transfer`
object, and is used for indexing callbacks more broadly than just
during transfers.

Rename `git_transfer_progress` to `git_indexer_progress`.
Update internal usage of `git_transfer_progress` to
`git_indexer_progreses`.
Safely deprecate `git_transfer_progress` and `git_transfer_progress_cb`
types, forwarding them to the new `git_indexer_progress` and
`git_indexer_progress_cb`.
The `git_push_transfer_progress` is a callback and as such should be
suffixed with `_cb` for consistency.  Rename
`git_push_transfer_progress` to `git_push_transfer_progress_cb`.
Safely deprecate `git_push_transfer_progress`, forwarding it to the new
`git_push_transfer_progress_cb` name.
@ethomson ethomson force-pushed the ethomson/transfer_progress branch from da3528b to ca909da Compare February 22, 2019 11:29
@ethomson

Copy link
Copy Markdown
Member Author

Sorry for breaking your PR 🙄

No worries; easy fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants