summaryrefslogtreecommitdiffstats
path: root/contrib/persistent-https
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2026-01-19 00:20:26 -0500
committerJunio C Hamano <gitster@pobox.com>2026-01-19 16:24:02 -0800
commit782a719e99b8a66ef7e05481a481ddfc329985b5 (patch)
tree51c0d0c0f4fb01556a00abf66c66a4e43c1bbc0c /contrib/persistent-https
parent9500b2131d29960d3fbd35559c063f7a74568875 (diff)
downloadgit-782a719e99b8a66ef7e05481a481ddfc329985b5.tar.gz
git-782a719e99b8a66ef7e05481a481ddfc329985b5.zip
remote: drop const return of tracking_for_push_dest()
The string returned from tracking_for_push_dest() comes from apply_refspec(), and thus is always an allocated string (or NULL). We should return a non-const pointer so that the caller knows that ownership of the string is being transferred. This goes back to the function's origin in e291c75a95 (remote.c: add branch_get_push, 2015-05-21). It never really mattered because our return is just forwarded through branch_get_push_1(), which returns a const string as part of an intentionally hacky memory management scheme (see that commit for details). As the first step of untangling that hackery, let's drop the extra const from this helper function (and from the variables that store its result). There should be no functional change (yet). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/persistent-https')
0 files changed, 0 insertions, 0 deletions