I'm not sure if there's another practical way - suggestions welcome. It could be that we need to provide additional explicitĬommand-line options for specifying the branch/tag/revision to avoid that, That part and because something=value is a valid shell command you You must use quotes around the URL if you're specifying a revisionĪnd/or branch because of the character, otherwise your shell will eat The current workaround for this particular example is to use this:ĭevtool add -version 2.4.2 mbedtls " git:///ARMmbed/mbedtls branch=mbedtls-2.4 rev=mbedtls-2.4.2"īy using the default git protocol rather than ssh, we avoid having to which avoids triggering 11390 or 11391. > Guidance and correction would be most appreciated.įor everyone's benefit, FYI Brian and I have talked offline, but thereĪre several bugs and opportunities for improvement here as it turns out. > would be nice to know how to do it "the right way" for the documentation > configuration specific for our platform. > where I'll then create a bbappend to add additional patches and > My goal is to set up a stock recipe off of the mbedtls-2.4.2 tag, > (E.g., just go to the sources directory, check it out and manually update > Is this a limitation of devtool, or is a better way to do this? > It still manages to get the wrong hash (not even the right branch). > devtool add -version mbedtls-2.4.2 mbedtls > git at :ARMmbed/mbedtls.git tag=mbedtls-2.4.2 > devtool add -version 2.4.2 mbedtls git at :ARMmbed/mbedtls.git > executing it correctly to pull the desired tag. > From there, I'm trying to create a new recipe, but I apparently am not > I've created a generic eSDK (poky and meta-openembedded) and installed it. > I'm trying to get up to speed on devtool. On Thursday, 20 April 2017 10:50:19 AM NZST Brian Kurle wrote: Next message: devtool and adding specific tag from repo.Previous message: devtool and adding specific tag from repo.Therefore, tags are meant to mark points in you history that do not change. When you make another commit in that branch, your tag still points to the original commit. When you do git tag xxxx in branchA, you mark a particular commit that is currently on top of that branch. devtool and adding specific tag from repo Paul Eggleton paul.eggleton at Tags do not point to branches, but rather to separate commits. If you get stuck, more in depth tagging documentation is available here.Devtool and adding specific tag from repo If you're new to Bitbucket, sign up for a Bitbucket Cloud account, create a repo and make a commit to take it for a spin. If you already use Bitbucket, start saving time with this new feature and start tagging (allthethings). If you are looking for lightweight tags, they can still be added via our API but are not currently available in the UI. In the future we will be expanding tagging from the UI with the ability to add custom messages to compliment any annotated git tag applied in the UI. Once ‘create tag’ is selected, the author and timestamp will automatically be recorded. In the details pane, on the right side of the commit view, you can see ‘current tags’ and ‘create tag’. To add a tag, navigate to a commit in your repository and click on the commit in need of a tag. If there’s a failing build, you might want to push some fixes before creating your tag! Commit’s build status: Double-check the build status of your commit.Branches page: Quickly check that all features scheduled for release have been merged into your main branch, before creating your tag.If you’re reading this thinking “ why would someone tag a commit from the UI? The command line works just fine for me.” Lets look at where you can save time and find commits that need tagging in Bitbucket without switching over to the command line: The name of the tag, date/time, and author can be applied to any commit. Add tags from the UI vs the command lineīitbucket users have asked us how they can cut out this back and forth and tag commits directly from Bitbucket Cloud’s UI, and today we’re launching this capability to add annotated git tags and regular mercurial tags directly to commits from the UI. This is a major pain (shakes fist at context switching). You find the commit and realize that it is missing a release tag, so you go to the command line – create and push the tag so you can tag the commit for the release, then go back to Bitbucket’s UI to view the tag and ultimately, do the release. Here’s a look at a hypothetical scenario for adding tags: You’re a release manager getting ready for a release so you navigate to Bitbucket’s UI and view all the commits, looking for the one that has all the features you want to include and has passing builds. If you change versions a lot, they are a life saver for an organization instead of just using branches, which commonly leaves you with lots of rarely used branches. They reduce complexity, clean up your branch workflow, and are a way to mark exact versions of commits. Git tags have become essential to a Git workflow to mark specific points in your Git history (like referencing a specific version of a project by tagging a commit for your release).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |