On 7/16/23 10:03, o...@c-mauderer.de wrote:
Of course the revision from two months back has to be available in
the repo. It doesn't really matter whether it's on master because the
code just worked or whether it's a RTEMS specific branch because
adaptions have been necessary.
You "it doesn't really matter" worries me a little bit. I'm not sure
this functionality is even supported hence my question above if you
have tested it yourself.
Yes, I use that regularly. For an (old) example, take a look at a branch
in the repo that I use to test GSoC work:
https://gitlab.com/c-mauderer/rtems-bbb/-/tree/6
I have a libs/rtems-libbsd submodule there that uses the revision
c9474c0b which is on a cm/20200726_fix branch in my clone of
rtems-libbsd. In the .gitmodules the branch is still set to "master".
Despite that, git can find thre right commit ID.
Cool! So it didn't work for me due to (i) my git bug or (ii) my git
doesn't supporting whatever or simply due to (iii) me making silly
mistake somewhere.
Will need to recheck this. Thanks for the info!
Karel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
