On Wed, Jun 26, 2024 at 8:35 PM Marc Schink wrote:
>
> On Tue, 2024-06-25 at 10:33 +0200, Antonio Borneo wrote:
> > On Mon, Jun 24, 2024 at 11:46 PM Marc Schink wrote:
> > >
> > > On Sun, 2024-06-23 at 10:27 +0200, Antonio Borneo wrote:
> > > > ...
> > > > - git2cl is only used for OpenOCD releas
On Tue, 2024-06-25 at 10:33 +0200, Antonio Borneo wrote:
> On Mon, Jun 24, 2024 at 11:46 PM Marc Schink 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
On Mon, Jun 24, 2024 at 11:46 PM Marc Schink 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 maintaine
On Sun, 2024-06-23 at 10:27 +0200, Antonio Borneo wrote:
>
> On Sat, Jun 22, 2024 at 9:20 AM Marc Schink wrote:
> > A more general question: what is the reason for integrating jimtcl
> > as a
> > submodule in the first place? According to repology it seems to be
> > widespread. We deprecated the
> a clean clone does not cause any issue.
The issue comes from old clones that still keep the reference to the old
submodule repo (if bootstrap was already called once).
Ah, thanks for that clarification, Antonio. That clears things up for me. :-)
On Sat, Jun 22, 2024 at 9:20 AM Marc Schink wrote:
> A more general question: what is the reason for integrating jimtcl as a
> submodule in the first place? According to repology it seems to be
> widespread. We deprecated the libjaylink submodule, what is the reason
> to keep jimtcl?
>
I'm not a
On Fri, Jun 21, 2024 at 8:09 PM Tommy Murphy
wrote:
> > The root cause is that .gitmodules entry for jimtcl was changed but
> > not the submodule itself and that the required checkout was not
> > available at the old repository.
>
> Sorry, but I'm still confused.
>
> After a clean checkout I see
On Fri, Jun 21, 2024 at 2:50 PM Antonio Borneo
wrote:
>
>
> On Fri, Jun 21, 2024 at 2:42 PM wrote:
>
>> ...
>>
>> Strange that jimtcl/DEVELOPING says that:
>>
>> Jim's sources are kept in Git Version Control System. Global repository of
>> Jim project is placed on this Web site:
>>
>> h
On Sat, Jun 22, 2024 at 04:33:42PM +0200, k...@aspodata.se wrote:
> I'm perfectly fine with perl, but cloning it didn't work.
Try this, it works with .git appended:
GIT_SSL_NO_VERIFY=1 git clone \
https://gitorious.org/openidserver-sqlite/openidserver-sqlite.git
--
Be free, use free (http://w
Paul Fertser:
> On Fri, Jun 21, 2024 at 02:57:44PM +0200, k...@aspodata.se wrote:
> > > But as you are an active user of OpenOCD, it would be nice if you give
> > > another try to install an openid for any further contribution or to review
> > > the patches in gerrit.
> >
> > Which version of Open
Hi Karl,
On Fri, Jun 21, 2024 at 02:57:44PM +0200, k...@aspodata.se wrote:
> > But as you are an active user of OpenOCD, it would be nice if you give
> > another try to install an openid for any further contribution or to review
> > the patches in gerrit.
>
> Which version of OpenID do you use ?
On Fri, Jun 21, 2024 at 2:59 PM wrote:
> Antonio:
> ...
> > I will send the patch on gerrit with your email as reported-by.
>
> Great.
>
> > But as you are an active user of OpenOCD, it would be nice if you give
> > another try to install an openid for any further contribution or to
> review
> >
A more general question: what is the reason for integrating jimtcl as a
submodule in the first place? According to repology it seems to be
widespread. We deprecated the libjaylink submodule, what is the reason
to keep jimtcl?
Best regards,
Marc
On Fri, 2024-06-21 at 14:31 +0200, Antonio Borneo wr
Tommy Murphy:
> > The root cause is that .gitmodules entry for jimtcl was changed but
> > not the submodule itself and that the required checkout was not
> > available at the old repository.
>
> Sorry, but I'm still confused.
...
I can recreate the problem by doing:
git co 7d6156fae8a398a3bd17a
> The root cause is that .gitmodules entry for jimtcl was changed but
> not the submodule itself and that the required checkout was not
> available at the old repository.
Sorry, but I'm still confused.
After a clean checkout I see this in .gitmodules:
[submodule "jimtcl"]
path = jimtcl
Antonio:
...
> I will send the patch on gerrit with your email as reported-by.
Great.
> But as you are an active user of OpenOCD, it would be nice if you give
> another try to install an openid for any further contribution or to review
> the patches in gerrit.
Which version of OpenID do you use
On Fri, Jun 21, 2024 at 2:42 PM wrote:
> ...
>
> Strange that jimtcl/DEVELOPING says that:
>
> Jim's sources are kept in Git Version Control System. Global repository of
> Jim project is placed on this Web site:
>
> http://repo.or.cz/w/jimtcl.git
>
I will inform the developer.
He used t
Tommy Murphy:
...
> But I just find it strange to change things when the root cause hasn't
> been identified.
The root cause is that .gitmodules entry for jimtcl was changed but
not the submodule itself and that the required checkout was not
available at the old repository.
...
> Might the proble
You can try this, on a clean clone, simulating that it was an old clone on
which you suddenly run an update:
git clone https://github.com/openocd-org/openocd
cd openocd
git checkout v0.10.0 -- .gitmodules
./bootstrap
It will fail because it cannot get access to the jimtcl required by current
Open
If the change is deemed to be innocuous then I guess that there's no harm in
adding it.
But I just find it strange to change things when the root cause hasn't been
identified.
I did this - a clean clone of the OpenOCD GitHub sources and then a (brute
force) grep of all files in `.git` for any me
Antonio Borneo:
> On Thu, Jun 20, 2024 at 10:15â¯PM wrote:
...
> Yes, we switched repo, but I also met this issue after the switch.
> I have run some quick test, and I cannot find any bad impact when adding
> one line in bootstrap
>
> echo "Setting up submodules"
> git submodule init
> +
On Thu, Jun 20, 2024 at 10:15 PM wrote:
> Tommy Murphy:
> > Are you sure that you're not using a very old clone of the repo?
> > The JimTcl submodule was switched from https://repo.or.cz/jimtcl.git to
> https://github.com/msteveb/jimtcl.git back in December 2020.
>
> Thanks, that was probably the
Tommy Murphy:
> Are you sure that you're not using a very old clone of the repo?
> The JimTcl submodule was switched from https://repo.or.cz/jimtcl.git to
> https://github.com/msteveb/jimtcl.git back in December 2020.
Thanks, that was probably the problem.
Doing the switch make bootstrap work wit
Are you sure that you're not using a very old clone of the repo?
The JimTcl submodule was switched from https://repo.or.cz/jimtcl.git to
https://github.com/msteveb/jimtcl.git back in December 2020.
https://github.com/openocd-org/openocd/commit/861e75f54efbcc1e0717192c6ddb120478d6c226
I just did this on Ubuntu 22.04.4 on Windows 10 WSL2 and didn't have any
problems:
```
git clone https://github.com/openocd-org/openocd
Cloning into 'openocd'...
remote: Enumerating objects: 81489, done.
remote: Counting objects: 100% (6117/6117), done.
remote: Compressing objects: 100% (748/748)
I did:
$ ./bootstrap
+ aclocal --warnings=all
+ libtoolize --automake --copy
+ autoconf --warnings=all
+ autoheader --warnings=all
+ automake --warnings=all --gnu --add-missing --copy
Setting up submodules
warning: redirecting to https://repo.or.cz/r/jimtcl.git/
warning: redirecting to https://r
26 matches
Mail list logo
