Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 739499
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T08:24:27+00:00 2026-05-14T08:24:27+00:00

What is the experience (good or bad) using Git for version control relating to

  • 0

What is the experience (good or bad) using Git for version control relating to how well different releases of Git work together?

To cut a short story long:

I am considering Git for some planned home projects, but due to my hodge-podge range of setups using default packages from repositories will mean being a full point release different. I plan to keep a master repository (which other people may be reading and branching from) on a server that runs Ubuntu 8.04 which means v1.5.x if I use the pakages from the standard repository (that may get upgraded to 10.04 in the coming months, which would mean the Git packages upgrading to 1.7.x), but my netbook runs the newer 9.10 which has Git v1.6.x. My main Windows machine I’ve not decided what to do with yet (as there is no package management to use it could either get any version directly, or I might use an Ubuntu VM for development).

As an extra complication, I’m likely to want to interact with a couple of projects currently on GitHub too (and perhaps drop some of my code there too as I intend for it to be open-source software).

I’m happy to compile up my own copies of what-ever version is best (i.e. the stable version closest what GitHub runs, presumably 1.7.x) if that is the only reliable way to proceed, but if I’m unlikely to experience problems pulling changes between 1.5/1.6/1.7 then I’d prefer to keep to the standard repository versions to make updates/upgrades of Git as painless as possible.

I’ve not found any reference to this after a few searches, which leads me to believe cross-version compatibility is good (if there were significant problems I’d expect there to be obvious mention in the release notes and to find posts in various places from people asking how to deal with issues).

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-14T08:24:28+00:00Added an answer on May 14, 2026 at 8:24 am

    When it come to the repository format and layout, I believe the last change was from Git 1.4.3 to 1.5.0.

    Jakub mentions here a few features that may be not supported depending on your Git version, but there shouldn’t be any incompatibility issue in term of “older version which could not be able to deal with repository created with newer version”.
    Git 1.5.x, 1.6.x and 1.7.x should all manage the same repository without any problems.

    Update 2017: I confirm a git repo 2.x still works with a git repo 1.7

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 379k
  • Answers 379k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer I hear you asking to get the "information of the… May 14, 2026 at 9:35 pm
  • Editorial Team
    Editorial Team added an answer This definitely works in Firefox. As such, it should work… May 14, 2026 at 9:35 pm
  • Editorial Team
    Editorial Team added an answer This feature of PHP is called Variable functions. The issue… May 14, 2026 at 9:35 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.