3/4/2023 0 Comments Iscream linux![]() Secondly, if your worry is that you forget, then hell, write a small shellīUT DO NOT MESS UP THINGS FOR OTHER PEOPLE. In fact, in manyĬases that's exactly what you want, namely you want to fetch the data Tags _first_ in order to decide what you want to fetch. _without_ fetching anything else, and you might indeed want to get the First off, you might want to get new tags This? You've introduced nothing but syntactic fluff, and you've made it How is this AT ALL different from just having a separate script that does > rsync -r -ignore-existing repo/refs/tags/. > Suggested solution: add '-tags' to git-pull-script You just never noticed, because Linux could never use tags atĪll due to the lack of privacy, except for big releases. Think) to pick the one last in the BK ChangeSet file, but that didn't make BK had a very strange form of merging, which was (I As mentioned, itįundamentally breaks the distributed nature, but that also means that itīreaks whenever two people use the same name for a tag, for example. No "you automatically get the tags when you get the tree", because the twoĪnd not making them separate breaks a lot of things. Tags are separate from the source they tag, and they HAVE TO BE. > Multiple users - not just me - would prefer that git-pull-scriptĪnd multiple users - clearly including you - aren't listening to me. Notion that tags are associated directly with the commit itself and It's that simple, and it does not introduce the _BROKEN_ It in a _sane_ manner: you tell git that you want a tag, and git fetches That solves exactly the case that Greg is complaining about, and it solves My modification, you test it, and you see if > pulled his 2.6.12.1 tree and and was wondering where the tag went.Īnd I suggested that if you want that, then you pull on the TAG. > tags in properly when doing a merge? Chris and I just hit this when I > Is there some reason why git doesn't pull the That's what we had in BK _AND IT DOES NOT WORK_! Pointless as anything but "Linus' official tags". Tags are notĪssociated with the tree, and they _cannot_ and _must_not_ be so, exactlyīecause that would make them global instead of private, and it wouldįundamentally make them not be distributed, and would mean that they'd be Pulling a regular head _cannot_ and _must_not_ update tags. Next in thread: Greg KH: "Re: Updated git HOWTO for kernel hackers".In reply to: Jeff Garzik: "Re: Updated git HOWTO for kernel hackers".Previous message: AM-Team: "New Secret Weapon Against Intruders!".Next message: Hans Reiser: "Re: reiser4 plugins".Linux-Kernel Archive: Re: Updated git HOWTO for kernel hackers Re: Updated git HOWTO for kernel hackers From: Linus Torvalds
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |