Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

repository.rb

  • Zeger-Jan van de Weg's avatar
    c830b8e3
    Client implementation for InfoAttributes · c830b8e3
    Zeger-Jan van de Weg authored
    Clients can now request the attributes from `$GIT_DIR/info/attributes`
    through Gitaly. The Gitaly migration is described in gitlab-org/gitaly#1082.
    
    The parser algorithm was implemented in a way it could handle both file
    contents or a File handle, and both were already tested.
    
    Other than that, using the boy scout rule, I've removed a class,
    InfoAttributes, as it was delegating everything to the parser and
    therefor wasn't really needed in my opinion.
    Client implementation for InfoAttributes
    Zeger-Jan van de Weg authored
    Clients can now request the attributes from `$GIT_DIR/info/attributes`
    through Gitaly. The Gitaly migration is described in gitlab-org/gitaly#1082.
    
    The parser algorithm was implemented in a way it could handle both file
    contents or a File handle, and both were already tested.
    
    Other than that, using the boy scout rule, I've removed a class,
    InfoAttributes, as it was delegating everything to the parser and
    therefor wasn't really needed in my opinion.