On Tue, Jul 15, 2025 at 04:41:33PM -0400, Rodrigo Vivi wrote:
> On Mon, Jul 14, 2025 at 06:50:07AM +0200, Lukas Wunner wrote:
> > That's exactly the same URL I'm using as well and "url_to_remote"
> > resolves it to the remote name without any issues.
> >
> > (The remote is named "torvalds" in my local repo.)
>
> Well, this really works inside dim... For some reason the version inside
> dimrc doesn't work well, but when I put a print inside dim_status function
> directly
>
> echo $(repo_to_remote linux-upstream)/master
>
> it indeed printed out
>
> origin/master
>
> So, just ignore my blocker here...
dim executes the function "load_config" (which loads dimrc) right at the
top of the script. At this point, the function "read_integration_config"
(which loads nightly.conf) hasn't been executed yet. Hence I'd expect
${drm_tip_repos[$repo]} to be empty.
What's confusing though is that function "url_to_remote" does seem to
know the linux-upstream URLs:
> rdvivi@rdvivi-mobl1:~/linux/maintainer-tools$ dim blah
> dim: Adding remote for linux-upstream repo from URLs:
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git
Maybe you're setting ${drm_tip_repos[]} in your dimrc or something?
Thanks,
Lukas
