geekhack
geekhack Community => Off Topic => Topic started by: SSIPAK on Wed, 14 May 2014, 02:38:28
-
Hey,
I have bunch of hw from introduction to java class that is due this friday. I was wondering if there is someone who can help me out with these and I will send you some gift for helping me out. Message me if you are interested. Thanks.
-
I don't want your money, but if you want, you can PM me a link to a private gist with the source code and specific questions. Assuming you have a github account. If not, you should get one and learn how to use it over the summer. I also have assignments due to Friday, but I'm in EU, so I'm half a day ahead of you if you're in America. I'll probably have some time to look at it tomorrow, since I have an assignment due in six hours and I've pulled an all-nighter in order to get it done on time.
-
+1 for using git, I started using it recently and while it was daunting at first it's dead easy once you get the hang of it. Had it save my arse the other day too.
-
i think you have to use tfs and svn before you can appreciate how common sense and usable git is.
-
i think you have to use tfs and svn before you can appreciate how common sense and usable git is.
I respectfully and completely disagree. I never defiled my mind with svn and I've only used git for version control and use it regularly and as it should: cheap branches all day every day.
-
i think you have to use tfs and svn before you can appreciate how common sense and usable git is.
I respectfully and completely disagree. I never defiled my mind with svn and I've only used git for version control and use it regularly and as it should: cheap branches all day every day.
I think he meant using SVN shows you how easy git is in comparison, I used SVN for a year before I switched and I'd totally agree.
-
Indeed. Pardon me. The all-nighter must have clouded my abilities to read.
Hope that didn't ruin my paper, which I just submitted.
-
As someone who uses SVN every day, I find git to be difficult to fit into my current workflow.
-
i think you have to use tfs and svn before you can appreciate how common sense and usable git is.
I respectfully and completely disagree. I never defiled my mind with svn and I've only used git for version control and use it regularly and as it should: cheap branches all day every day.
I think he meant using SVN shows you how easy git is in comparison, I used SVN for a year before I switched and I'd totally agree.
You don't even need to switch entirely. You can svn clone any repository on GitHub :trolleybus:
-
I think SVN and Git were built for different processes and software development teams. Generally, SVN is centralized control and Git is de-centralized. Indeed, we can force them to work on the other way around but it is not supposed to be. If you have a team working on the same repository, then SVN is a good choice, but if you are working alone or your team members are following different repositories, then Git is a good choice. However, if you are working alone and you already had a reliable SVN server, then you can see that SVN is very good too.
The OP is asking how to solve the Java HW. So I wish he can find someone to help him with that. Anyway, Java is widely used and probably he can seek for more help on stackoverflow anytime.
-
I don't see a single benefit of having source control centralized.
Why on earth is SVN a good thing if you're working as a team? Git has really great support for branches and doesn't cause a cluster**** every time you want to merge branches like SVN is known for. That will allow people to work on their own branches and merge them together with great ease. Have you ever pulled a git repository? Those DAG structures are fast as hell! You can even commit without being connected to the SVN server, or even the Internet for that matter.
If you have a linux box available and ssh keys setup a git repository is done in fraction of a second: git init --bare
SVN is only good if all you know is SVN, but even then you're at a loss because you have to adopt to the git way of doing things: branch ALL the things! Eventually, you'll get that job where people aren't working on a legacy code base.
SVN might be a good choice if you're forced to use it, but for that you still have git-svn.