Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic

Re^3: just wanted to show what I managed to write with your help

by choroba (Chancellor)
on Nov 12, 2012 at 13:09 UTC ( #1003436=note: print w/replies, xml ) Need Help??

in reply to Re^2: just wanted to show what I managed to write with your help
in thread just wanted to show what I managed to write with your help

Believe me, the overhead of using a version control system is negligible compared to the overhead of not using it.
لսႽ ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ
  • Comment on Re^3: just wanted to show what I managed to write with your help

Replies are listed 'Best First'.
Re^4: just wanted to show what I managed to write with your help
by perltux (Scribe) on Nov 12, 2012 at 13:17 UTC
    I'm sure you are right, but the overhead of first learning how to use it is not negligible! :)

    Seriously I certainly see the point in using one once more than one person works on the code, but right now it's only me.

    Again if anyone wants to collaborate, just let me know and I'll start learning how to use git and github.

      I would second choroba's suggestion to use a revision control system of some sort (git, svn). It allows you to 'erase' mistakes or back track to a point where your code was working. It is also nice to be able to take multiple divergent paths when testing out if something will work, and to be able to select the parts that work best.


      As well as code colaboration, a project Wiki and issue tracking git is also very handy for people wanting to download your works:

      git clone

      FWIW, learning git isn't too critical, as long as you archive your directory before adding new features and bump the version (hey, its The Git Parable (how git works, inventing git ))

      you can turn zip-files into a git repo when/if there is a demand ( if gitpan can do it :)

      But if you do want to learn it I recommend (Git HowTo TOC in spoiler)

      • 1. Preparation
      • 2. The final preparation
      • 3. Creating a Project
      • 4. Checking the status of the repository
      • 5. Making changes
      • 6. Staging the changes
      • 7. Staging and committing
      • 8. Commiting the changes
      • 9. Changes, not files
      • 10. History
      • 11. Aliases
      • 12. Getting older versions
      • 13. Tagging versions
      • 14. Discarding local changes (before staging)
      • 15. Cancel Staged changes (before committing)
      • 16. Cancelling commits
      • 17. Removing a commit from a branch
      • 18. Removing the oops tag
      • 19. Changing commits
      • 20. Moving files
      • 21. More information about the structure
      • 22. Inside Git: .Git directory
      • 23. Git inside: Direct work with git objects
      • 24. Creating a Branch
      • 25. Navigating Branches
      • 26. Changes to master branch
      • 27. View the different branches
      • 28. Merging
      • 29. Creating a conflict
      • 30. Resolving Conflicts
      • 31. Relocating as an alternative to merging
      • 32. Resetting the style branch
      • 33. Reset of the Master branch
      • 34. Rebase
      • 35. Merging to the Master branch
      • 36. Multiple repositories
      • 37. Cloning repositories
      • 38. Examine the cloned repository
      • 39. What is origin?
      • 40. Remote branches
      • 41. Changing the original repository
      • 42. Fetching changes
      • 43. Merging pulled changes
      • 44. Pulling and merging changes
      • 45. Adding a tracking branch
      • 46. Bare repos
      • 47. Adding a remote repository
      • 48. Submitting changes
      • 49. Removing common changes
      • 50. Placing your git repository
      • 51. Sharing repositories
      • Thank you!

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1003436]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (3)
As of 2017-05-22 16:22 GMT
Find Nodes?
    Voting Booth?