Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 26 |
Nodes: | 6 (0 / 6) |
Uptime: | 92:11:44 |
Calls: | 483 |
Calls today: | 1 |
Files: | 1,073 |
Messages: | 97,705 |
On Thu, Mar 20, 2025 at 06:10:35PM +0100, Raphael Hertzog wrote:
Hello Gregor,
On Sun, 12 Jan 2025, gregor herrmann wrote:
On Sat, 11 Jan 2025 12:00:27 +0100, Raphael Hertzog wrote:I can certainly sympathize with that. I don't have any strong personal
Given that the "upstream" branch name cames from the git-buildpackage andIn theory, yes. In pratice, quoting myself:
that it's git-buildpackage which introduced "upstreamvcs", it seems fair >> > > to me to standardize on this name.
| As a data point, the Debian Perl Group is using "upstream-repo" for
| this additional remote in its tools since December 2013.
Not that one is better than the other, and although I like to follow
git-buildpackage in general, having to change the names on 4000+
remotes on dozens of developers' machine is annoying.
preference in the name but since the goal is to standardize across tools,
we need to pick one.
Can you point out which tools in the Perl group use that remote name?
How easy is it to tweak those tools to perform the rename of the remote
in some dynamic fashion?
On the other side, we could check whether Guido would be willing to update >> git-buildpackage to use "upstream-repo" as default? I don't know sinceThe work within gbp is almost zero. I'm aware of some scripts that rely
when "uptsreamvcs" is a thing and whether changing the default again would >> have serious drawbacks.
on the naming though and we don't know what else exists outside of gbp
(and there's also users outside Debian) so if we don't *have* to change
the name that would be better.
I (finally) hada quick look, and it should be fairly easy to add the
rename to dpt-upstream-repo, which is also called by our .mrconfig
setup. Looks like a quick DebCamp project.