Hello, On Fri 27 Dec 2024 at 01:20am -08, Xiyue Deng wrote:
> Sean Whitton <spwhit...@spwhitton.name> writes: > >> Hello, >> >> On Thu 26 Dec 2024 at 03:23pm -08, Xiyue Deng wrote: >> >>> Package: dh-make-elpa >>> Version: 0.19.5 >>> Severity: wishlist >>> >>> Currently dh-make-elpa suggests using "upstream" as upstream remote name >>> in its manpage. This works, but could be confusing as DEP-14 also >>> suggests using "upstream/latest" as the branch name for upstream repo. >>> I would like to suggest using "upstreamvcs" as upstream remote name >>> instead, which is also used by dh-make. >> >> I'd prefer to leave it as it is. The 'vcs' in 'upstreamvcs' is >> redundant, because of course it's a VCS -- it's a git remote. >> > > Right. It's just that this name clash with "upstream" or > "upstream/latest" is kind of inconvenient, especially in magit (I should > have mentioned this in the report) that when you try to switch to a > branch and as you try to auto-complete for "upstream", it shows all > remote branches starting with upstream as well, which can be confusing. > > Using a different name helps a little, and I guess this could be why > dh-make started suggesting "upstreamvcs". It doesn't have to be that > name, of course. Anything different from "upstream" helps :) Thanks for explaining. I think with git you just have to deal with this across the board. For example dgit-repos uses a remote branches namespace called 'dgit' and the branches are 'dgit/sid', 'dgit/bookworm' etc., so you frequently have to deal with 'dgit/dgit/sid'. So, I'm not sure trying to help in this way is a job for dh_make_elpa. If someone regularly runs into this problem, they can just use a different one themselves, the manpage name is just a recommendation, after all. (I'm a bit biased here because I don't think we should be maintaining upstream branches at all, for most packages, as you know from reading some of my dgit tutorial manpages.) -- Sean Whitton
signature.asc
Description: PGP signature
