Skip to content
Snippets Groups Projects
Select Git revision
  • dc1d0e0c7fffa5109048ac52a67aa97bb362ae3a
  • aosp-new/aosp-new/main default
  • main
  • stable
  • aosp-new/stable
  • master
  • maint
  • repo-1
  • qc-stable
  • clo-stable
  • v2.31
  • v2.30
  • v2.29.9
  • v2.29.8
  • v2.29.7
  • v2.29.6
  • v2.29.5
  • v2.29.4
  • v2.29.3
  • v2.29.2
  • v2.29.1
  • v2.29
  • v2.28
  • v2.27
  • v2.26
  • v2.25
  • v2.24.1
  • v2.24
  • v2.23
  • v2.22
30 results

docs

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Mike Frysinger authored
    Going purely on upstream package release cycles doesn't tell the whole
    story: a lot of people run LTS distros which will have older versions
    of software we want to support.
    
    Build out a table for us to quickly reference when making decisions as
    to what versions of git/python we want to support, and when we can drop
    them.  This will also help to refer users to as why we made a specific
    decision that might be affecting them.
    
    Change-Id: I7aea24bbefd50e358aeacf11e8c15a346c8fb8a9
    Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/254572
    
    
    Tested-by: default avatarMike Frysinger <vapier@google.com>
    Reviewed-by: default avatarDavid Pursehouse <dpursehouse@collab.net>
    3645bd24
    History