diff options
| author | Matthew Leeds <mwleeds@protonmail.com> | 2019-01-13 21:04:05 -0800 |
|---|---|---|
| committer | Matthew Leeds <mwleeds@protonmail.com> | 2019-01-13 21:37:14 -0800 |
| commit | e2cab23fa60a9177773998d7fc6abd24ad184941 (patch) | |
| tree | 09d834aa157485fc2c8747b8931bc81c66698c0e | |
| parent | 6a7b074946c8ca1ea0cf4f2b9a385cd22f709c87 (diff) | |
| download | flatpak-delete-old-comments.tar.gz | |
dir: Delete some outdated commentsdelete-old-comments
It's no longer true that it's the pull code's job to resolve a ref to a
specific commit. Ever since commit 66eee3c2c this is the job of the
resolve_ops() function used by FlatpakTransaction (at least, when a
transaction is being used). So update a couple comments to avoid
confusion.
| -rw-r--r-- | common/flatpak-dir.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/common/flatpak-dir.c b/common/flatpak-dir.c index 5a905c3e..eb17b768 100644 --- a/common/flatpak-dir.c +++ b/common/flatpak-dir.c @@ -7841,8 +7841,6 @@ flatpak_dir_install (FlatpakDir *self, flatpak_flags |= FLATPAK_PULL_FLAGS_SIDELOAD_EXTRA_DATA; - /* Don’t resolve a rev or OstreeRepoFinderResult set early; the pull - * code will do this. */ if (!flatpak_dir_pull (self, state, ref, opt_commit, NULL, subpaths, child_repo, flatpak_flags, @@ -7884,8 +7882,6 @@ flatpak_dir_install (FlatpakDir *self, if (!no_pull) { - /* Don’t resolve a rev or OstreeRepoFinderResult set early; the pull - * code will do this. */ if (!flatpak_dir_pull (self, state, ref, opt_commit, NULL, opt_subpaths, NULL, flatpak_flags, OSTREE_REPO_PULL_FLAGS_NONE, progress, cancellable, error)) |