Does anybody know how to determine whether a certain git commit, for example this one from this issue, was rolled into a particular Android release such as 2.2 Froyo?
Thanks!
My one suggestion is to just look at the shortlog of the appropriate branch (that's froyo-release; I'm guessing froyo is a maintenance branch) and see if the commit's in the shortlog. The commit in question is way, way back - on the 143rd page of the shortlog. I found it just by skipping back until the dates were right. Not very fancy.
I'm guessing this is all you can do with gitweb, though it is under pretty active development, so perhaps someday it'll get that "Branches: " feature from gitk. #Jakub Narebski is fairly active on SO; he might be able to provide a more definitive answer. (not sure if #-notification works in answers or just comments)
Related
I developing an app in Android Studio for a uni assignment. Unfortunately I seem to have gone down a bit of a blind alley and need to go back a few commits. But for reporting purposes I will need to keep a reference to the code I will be discarding and refer back to it on what I was doing, the problems I ran into etc.
So before I go back, can I be sure that the previous code will still be able to be viewed / referenced, even if it is not being used. I just want to make sure before I do anything. My experience with git version control in AS so far is simply making commits and pushing to github. This will be the first time going back or branching off so to speak.
Thanks
I am working on a project with one of my teammates. Today I just observed a very strange thing which is this *(Asterisk) with the Author Name in version control of the Android Studio Log window.
Normally I take the things related to git or version control seriously
so after merging I double-checked the changes of that
*(Asterisk) commit and the changes were there after merging. So
technically there is nothing wrong with the code and everything seems
perfect.
But still, if anyone knows what this *(Asterisk) means I would love to hear your thoughts?
Thanks in advance :)
It means that the author and commiter are different. Can happen, for example, if A cherry-pick's B's commits, or if A rebases a branch containing commits by B.
In the commit description (in the lower right) you should see, below the message and author, something like "Commited by XXXX".
today it's a shorter question I'd like to ask, to hear your opinions as I suppose some do this differently than others.
First of all,, I have an Android Studio project and am rather a novice on this subject of Android Development. That's why slight changes in the java or xml files could and did make my latest app unstable/ crashing.
Therefore I was asking myself wether Android Studio offers a way to backup stable builds - I could imagine this like a save-as option where you backup the working version and continue working on the the one but have a stable one backed up.
I know there's the export project function but I tried it out a couple of times and having worked on a project on the same device before, prior to reimporting a project causes an error and that's not the way I guess you should handle it in this situation.
I was looking at Google Cloud for using both version control and the option to commit new versions to the trunk and update them at a different location (different device). If that's the solution you propose, I need to look more closely into the documentation to get it up and running (set up the repository already but no clue how to commit changes/ versions).
So, long story short, what tool/ option do you prefer to have an export and a version control option unified for Android Studio?
Interested to hear and thankful for any advice on that!
There are multiple solutions,
Just find your solution/project in your file explorer and back it up, if you need it again just open the project with Android Studio. (not the most popular one)
Use a version control system like git. Link to tutorial (This is the most popular one), If u are unfamiliar with git, just google it and there are tons of examples and documentation. With git you can tag commits and after u mess up revert to the tagged commit
Git is the simpliest.
It's supported by AndroidStudio and later on you can upload your project to GitHub to access it from anywhere.
You can use it with terminal and shorcut keys, incons as well.
You also can make separate branches in order to make and test more versions parallely.
For more info take a look at: https://git-scm.com/about
and of course github: https://github.com/
Regards,
Cs
I've been noticing for the last month or so that users of my Android app are receiving partial updates. What I mean by this is that their version is up to date and has most of the features that I had made live, but at the same time would still have code that I had changed weeks earlier. This did not affect users that did a clean install though, just the 99% that probably update an app like a normal user would. I could see how this could easily be caused by a lapse of concentration while using "git add" however I've exclusively used "git add -A" for probably the last two months so this is not the case. Recently I got fed up enough with it that I purposely changed some of the log statements here and there just so that if I ran into another user who's phone had partially updated, I could check it out and see what files were up to date or not. Amazingly, I found a mix and match of updated and outdated files. I contacted Google via chat and they said that they would transfer me to an email conversation with a technical representative, but I haven't heard back yet. Has anyone else encountered this issue and how would you go about solving this?
So I have managed to get a couple apps up on the marketplace only to have a stray thought of what is the best way to go about managing my projects/apps within eclipse to accommodate future updates to the marketplace. My question resides within Eclipse and what to do with my projects/apps as I apply updates.
Do I simply copy my project/app, paste it and the increment the version information accordingly? Or am I continuously working on my published project/app? Or...Is there a recommended/preferred method of going about this. Since they are up and good on the marketplace I am leery of doing something that will cause problems for me later on down the line.
And don't change the package name....correct?
This is what I currently have on the Marketplace...
Wind Chill Calculator
True Love Game
First of all, everyone's posts were very helpful and I have spent some time looking over documentation through the links provided.
So...and brace for impact as I say this. Being one who has NEVER used any form of SCM for my projects this is all new to me (as everyone's faces cringe), which is why I am asking the original question in the first place. I hate to say tell me anything without doing my research...so within the past few hours using git within eclipse I have gleamed the following:
Team > Share Project ...ignores...any tags(for version info)which is what I am after...commits...THEN
Clone? File -> Import -> Git -> Git Repository at this point once I have cloned my project do I create a new tag with the new version info, and go through the commit process again? If this is the case I now have two items in my Git Repository. One of which has the single tag of 1.0, and the other item which contains two tags 1.0 and 1.1, and when I look at the history I see two tags Version 1.0 and Version 1.1. Then I just switch between the resources I need from within the repository?
I just want to make sure my process is correct before I begin to implement some of this on existing projects that are pretty extensive already. As for the rest I am just going to learn on the fly...branches
You might want to use a revision control system like SVN or git or one of dozens of other options, and continuously update the single project in Eclipse. The benefit of using source control is that you can branch into a new project for major changes, update your existing code for minor changes, and tag the branches so you can revert back to an old snapshot in the future.
I personally use bitbucket which is hosted remotely and is free. It supports SVN and Mercurial.
No, dont change the package name, that will make it new app, instead of upgrade of original.
Use a version control system, like SVN.
Manage Tags for a complete working state of code(through svn), so you can always revert back to that tag.
When ready for new release, increment version no. etc and update on market...
EDIT After addition in question:
Don't get much confused with various GIT/SVN working.. There main purpose is that they will allow you to switch your code back and forth to any point in past, that allows you to code in a way properly knowing that you can always revert back to a Working state.. and it is definitely of much more benefit in a Team , when multiple people are working on same codebase and possibly same files...
Being a long-time user of SVN, I recommend subclipse (svn for eclipse). When you're ready to release another version of your app, create a 'tag' for the release version and you'll always be able to go back to that exact version.
SVN has excellent docs. There is also TortoiseSVN for repo work outside of eclipse.