Hi Bruno,
Bruno Haible writes:
> It would still be wrong when a package is using one of the "stable" branches
> of gnulib.
[...]
> Here's what I'm committing. Let me know if it does not work in your case.
Right, this solution looks better. I haven't tested it but it looks like
good behavior to
Collin Funk wrote:
> > It would be nice to cover both "master" and "main". I think that would
> > cover 99% percent of cases.
It would still be wrong when a package is using one of the "stable" branches
of gnulib.
Marc Nieper-Wißkirchen wrote:
> I am not an expert in git, but here is some informa
Am Fr., 16. Aug. 2024 um 20:51 Uhr schrieb Collin Funk <
collin.fu...@gmail.com>:
> Hi Marc,
>
> Marc Nieper-Wißkirchen writes:
>
> > ./gitsub.sh upgrade
> >
> > fails when submodules are present where the master branch is not called
> > "master" but something else, e.g. "main", which becomes inc
Hi Marc,
Marc Nieper-Wißkirchen writes:
> ./gitsub.sh upgrade
>
> fails when submodules are present where the master branch is not called
> "master" but something else, e.g. "main", which becomes increasingly common.
>
> The branch name "origin/master" is currently hardcoded in gitsub.sh.
It wo
