Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 43 |
Nodes: | 6 (0 / 6) |
Uptime: | 100:29:02 |
Calls: | 290 |
Files: | 905 |
Messages: | 76,508 |
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.
Sean Whitton <spwhitton@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 :)