On Wed, Jun 26, 2024 at 8:35 PM Marc Schink <d...@zapb.de> wrote:
>
> On Tue, 2024-06-25 at 10:33 +0200, Antonio Borneo wrote:
> > On Mon, Jun 24, 2024 at 11:46 PM Marc Schink <d...@zapb.de> wrote:
> > >
> > > On Sun, 2024-06-23 at 10:27 +0200, Antonio Borneo wrote:
> > > > ...
> > > > - git2cl is only used for OpenOCD releases. We could keep it as a
> > > > submodule and change the default of bootstrap to no-submodule.
> > > >   git2cl is apparently not maintained anymore, so it could even
> > > > be
> > > > copied in our code, but since it's GPL2.0-only I prefer keeping
> > > > it
> > > > outside!
> > >
> > > Where do we actually use git2cl? The ChangeLog file (also in
> > > releases)
> > > is "empty" and we have a seperate (manually generated) NEWS file
> > > anyway.
> >
> > I don't know all the alchemies run by Paul for a release, but if you
> > download a
> > release like openocd-0.12.0.tar.bz2 from sourceforge you will see it
> > contains a
> > ChangeLog that is 2093189 bytes.
>
> Ah, okay. Btw, it's not available in the "releases" on GitHub.

Github is not the official repository of OpenOCD.
I think the releases there are autogenerated by GitHub.

>
> > It's only relevant for the release and I think Paul could accept
> > using adding a
> > parameter only for the release, like:
> > ./bootstrap submodule
> > or
> > ./bootstrap withsubmodule
> >
> > For all the other users and for ACI there would be no need to
> > download and use
> > this submodule, so bootstrap by default could ignore it.
> >
>
> Yep, sounds good. I will come up with some changes these days.

Thanks,
Antonio

Reply via email to