Some of the older ebuilds still reference the git:// scheme in the "live ebuild" case: btrfs-progs-4.4.1.ebuild: EGIT_REPO_URI="git://repo.or.cz/btrfs-progs-unstable/devel.git" btrfs-progs-4.9.1.ebuild: EGIT_REPO_URI="git://repo.or.cz/btrfs-progs-unstable/devel.git" btrfs-progs-4.10.2.ebuild: EGIT_REPO_URI="git://repo.or.cz/btrfs-progs-unstable/devel.git"
What is the point in updating the older ebuilds in a code path that will never execute?
(In reply to Mike Gilbert from comment #1) > What is the point in updating the older ebuilds in a code path that will > never execute? I was wondering the same...
Feel free to update them if this really bothers you. It should be harmless either way.