hey Zoran! On Wed, Nov 28, 2018 at 7:01 PM Zoran Stojsavljevic <zoran.stojsavlje...@gmail.com> wrote: > > > But again this is very different from the initial problem you are > > reporting, which is just a misunderstanding of git tags and commits. > > Nicolas, > > Your problem is that you are too emotional. Period. I clearly
First, I don't think I have a problem on this specific topic. And then I am pretty sure I am not emotional. I have only raised technical details/answers in my message. There was no emotion, it was just facts. > explained what my problem is. For some YOCTO github repos, certain git > commands DO NOT work. Nothing I did misunderstand, you just do not > read my emails enough carefully. If you go back on on my initial > email, and try it yourself, you'll see that there are commands which > are not working. Such as git describe, or git tag. Myself and a few others have tried to explain that these commands work perfectly well actually, unlike what you think. When running "git tag" on a repo that does not have any tag, it just doesn't return anything, so what you are seeing is the proper behavior. Same thing with "git describe". So the problem with the repo you have mentioned is that there is no tag published. That's it. Nothing wrong with git, or github, or Yocto. > > Here is the description of git tag commands. For you to learn (please, > read it carefully and exercise on the given example): > https://www.atlassian.com/git/tutorials/inspecting-a-repository/git-tag > > Before writing nonconclusive accusations, please, check what I am I am sorry if you thought it was accusation. It was , for me, a technical discussion. And I was trying to bring a few clarifications. > writing above, on my initial email. Maybe I am doing something wrong, > but I do not think so. For me, kernel.org tree perfectly works, and it > is perfectly aligned with git commands and .git directory. No, you are not doing anything wrong. > > With ALL git commands I am using. > > Thank you, > Zoran Stojsavljevic > _______ > On Wed, Nov 28, 2018 at 2:11 PM Nicolas Dechesne > <nicolas.deche...@linaro.org> wrote: > > > > On Wed, Nov 28, 2018 at 1:53 PM Zoran Stojsavljevic > > <zoran.stojsavlje...@gmail.com> wrote: > > > > > > > This is what your opinion is. Which seems to be vastly overestimating > > > > its own importance. > > > > > > I do not think you understood what I am trying to advertise. The > > > unification. In other words: > > > If I use kernel.org, I use git tool. > > > If I use YOCTO Poky, I would like to use git tool. > > > For all YOCTO repos, I would like to use git tool. > > > > You mean OpenEmbedded Layers, not Yocto repo here. I think 99.9% > > (maybe 100%) of the public OE layers are available as git repo. So you > > can (in fact you have to) use git for any OE layer. > > > > > > > > Not repo, kas, or other tools. Not particular tools, assigned to > > > particular tasks, for particular build systems. > > > > I think you are confused. There are hundreds of OE layers out there, > > maintained by developers, companies, communities, ... Poky is a > > reference implementation maintained by the Yocto Project. Building a > > custom Linux distro using Yocto Project means that you need to pull a > > certain amount of layers based on what you are doing. Most of the time > > each of these layers are hosted in their own *git* tree. For Poky we > > create a *new* git tree that results of the "merge" of all the > > dependent layers. However the OE core is maintained in their own tree > > and bitbake as well. > > > > the tools you mentioned here, like repo, kas, .. are not equivalent to > > git. they are helpers, wrappers, tools that can be use to combine many > > individual git repo to form a single workspace, so that you have all > > the layers you need in a single workspace to build your own custom > > distro. > > > > The Yocto Project does not recommend any specific tool to create such > > workspace, and people are using various solutions. There are on-going > > discussions in YP/OE to pick one tool and promote it, but no > > conclusion so far. > > > > But again this is very different from the initial problem you are > > reporting, which is just a misunderstanding of git tags and commits. > > > > > > > > Since I would like to invest time and effort in ONLY one, > > > comprehensive tool, and discard all other tools which are not up to > > > the complex challenges I have. So this is why I sent initial email, in > > > first place, > > > > > > Thank you, > > > Zoran > > > _______ > > > On Wed, Nov 28, 2018 at 12:25 PM Josef Holzmayr > > > <holzm...@rsi-elektrotechnik.de> wrote: > > > > > > > > Hello Zoran, > > > > > > > > On Wed, Nov 28, 2018 at 12:00:22PM +0100, Zoran Stojsavljevic wrote: > > > > > I am (almost) perfectly aligned with kernel.org, and I (personally) > > > > > decided to use git. Since I start understanding importance of Linus. > > > > > Linux officers and their Linux philosophy. > > > > > > > > You are free to choose your workflow as you please. > > > > > > > > > Now... Answers to your email. KAS (Siemens developed tool by Jan > > > > > Kiszka and his crew) is the supplement for the fast/quick building the > > > > > YOCTO, to use ONLY rootfs. NOT kernel. NOT aligned with the git tool. > > > > > Not applicable for purposes as git. > > > > > > > > It is a tool that serves one purpose. It does that job well. > > > > > > > > > On the other note, repo is GOOGLE tool. Promoted by them. Most of the > > > > > ARM followers (such as Toradex) use repo tool. > > > > > > > > Thats what they choose. > > > > > > > > > You say: I talk to the wrong crew. I think opposite. I am giving the > > > > > generic message via YOCTO email list, to avoid hundreds of particular > > > > > emails, so we can unify the effort. Which is not minor. Rather > > > > > opposite: major. > > > > > > > > > > Since, I guess, this is of the major importance. For YOCTO survival. > > > > > The direction is one: git tool. For all YOCTO developers. IMHO. > > > > > > > > This is what your opinion is. Which seems to be vastly overestimating > > > > its own importance. > > > > > > > > > Stefano, > > > > > > > > > > You, as major official representative of U-Boot philosophy (and > > > > > Wolfgang's Denk right hand), do not take sides, rather ad-hoc > > > > > approach. For you, this topic is not important. Appreciated your help. > > > > > > > > By now, you are telling other people who have been doing thwir work > > > > successfully for decades how to do their jobs. > > > > Actually, telling off one of the core contributors and community members > > > > with "This is not for you" is plain rude. > > > > > > > > > I am asking here for much higher awareness. YOCTO better survival in > > > > > The Future. > > > > > > > > We are doing quite well at the moment, thank you. > > > > > > > > So if you have a proposal on how to improve things, feel free to share > > > > it. Go ahead and lead on how to use that proposal by doing your own > > > > upstream work, showing how emplying your proposal makes it better and > > > > more usable. > > > > > > > > Just getting onto a mailing list and saying "You're doing it wrong > > > > because it doesn't suit my workflow", again, is quite rude. > > > > > > > > Greetz. > > > > > > > > PS: yes, this mail is explicitly meant to support Stefano. > > > > > > > > > > > > > > Thank you, > > > > > Zoran > > > > > _______ > > > > > On Wed, Nov 28, 2018 at 10:52 AM Stefano Babic <sba...@denx.de> wrote: > > > > > > > > > > > > Hi Zoran, > > > > > > > > > > > > On 28/11/18 10:17, Zoran Stojsavljevic wrote: > > > > > > > Hello YOCTO people, > > > > > > > > > > > > > > I would like to use standard git tool while using all the Yocto > > > > > > > layers. NOT only Poky repository (which, I believe, works all the > > > > > > > way > > > > > > > with git tools), but as much as possible with other github > > > > > > > proprietary > > > > > > > repos and layers. Since I am not able to execute git commands > > > > > > > using > > > > > > > some number of proprietary repos over github. > > > > > > > > > > > > > > As example, I'll use meta-bbb repository. > > > > > > > https://github.com/jumpnow/meta-bbb.git, after cloning the > > > > > > > following > > > > > > > happens (chosen, since it has at least dozen of branches): > > > > > > > > > > > > > > After cloning, I did not get anything from the following commands, > > > > > > > being in the root of the meta-bbb repo, namely: > > > > > > > > > > > > > > [user@fedora28-ssd meta-bbb]$ pwd > > > > > > > /home/user/projects2/beaglebone-black/yocto-master/meta-bbb > > > > > > > [user@fedora28-ssd meta-bbb]$ git describe > > > > > > > fatal: No names found, cannot describe anything. > > > > > > > > > > > > I understand, but why is this an issue in Yocto project ? The > > > > > > maintainer > > > > > > does not use tags and git describe is fast useless. > > > > > > > > > > > > You should contact layer's maintainer and ask for that. Anyway, > > > > > > outside > > > > > > poky, tags are quite unused in layers. > > > > > > > > > > > > > [user@fedora28-ssd meta-bbb]$ git tag > > > > > > > [user@fedora28-ssd meta-bbb]$ git checkout thud > > > > > > > Branch 'thud' set up to track remote branch 'thud' from 'origin'. > > > > > > > Switched to a new branch 'thud' > > > > > > > [user@fedora28-ssd meta-bbb]$ git checkout sumo > > > > > > > Switched to branch 'sumo' > > > > > > > Your branch is up to date with 'origin/sumo'. > > > > > > > [user@fedora28-ssd meta-bbb]$ git describe > > > > > > > fatal: No names found, cannot describe anything. > > > > > > > [user@fedora28-ssd meta-bbb]$ > > > > > > > > > > > > > > The rationale behind this request: git is the powerful tool which > > > > > > > should work and be solely used for YOCTO layers' synchronization. > > > > > > > In > > > > > > > other words, YOCTO should give some tools' (namely git) > > > > > > > unification > > > > > > > guidelines in some way. :-) > > > > > > > > > > > > It is clear that a tool to maintain the layers in sync is required, > > > > > > but > > > > > > it is quite independent how the layers (and many are proprietary > > > > > > layers) > > > > > > are built. So you can use "repo" or "kas" (my preferred one) for > > > > > > that. > > > > > > > > > > > > Best regards, > > > > > > Stefano Babic > > > > > > > > > > > > -- > > > > > > ===================================================================== > > > > > > DENX Software Engineering GmbH, Managing Director: Wolfgang > > > > > > Denk > > > > > > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, > > > > > > Germany > > > > > > Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: > > > > > > sba...@denx.de > > > > > > ===================================================================== > > > > > -- > > > > > _______________________________________________ > > > > > yocto mailing list > > > > > yocto@yoctoproject.org > > > > > https://lists.yoctoproject.org/listinfo/yocto > > > > > > > > -- > > > > ——————————————— > > > > Josef Holzmayr > > > > Software Developer Embedded Systems > > > > > > > > Tel: +49 8444 9204-48 > > > > Fax: +49 8444 9204-50 > > > > > > > > R-S-I Elektrotechnik GmbH & Co. KG > > > > Woelkestrasse 11 > > > > D-85301 Schweitenkirchen > > > > www.rsi-elektrotechnik.de > > > > ——————————————— > > > > Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393 > > > > Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg > > > > Ust-IdNr: DE 128592548 > > > > > > > > _____________________________________________________________ > > > > Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363 > > > > Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg > > > > USt-IdNr.: DE 128592548 > > > > > > > -- > > > _______________________________________________ > > > yocto mailing list > > > yocto@yoctoproject.org > > > https://lists.yoctoproject.org/listinfo/yocto -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
