[ET Trac] [Einstein Toolkit] #248: Enhance GetComponents functionality when dealing with git branches

[Einstein Toolkit]

#248: Enhance GetComponents functionality when dealing with git branches
----------------------------+-----------------------------------------------
  Reporter:  bmundim        |       Owner:  eric9       
      Type:  enhancement    |      Status:  accepted    
  Priority:  minor          |   Milestone:              
 Component:  GetComponents  |     Version:              
Resolution:                 |    Keywords:  git branches
----------------------------+-----------------------------------------------

Comment (by bmundim):

 Replying to [comment:10 eschnett]:
 > This begins to become quite complex. First, there is the option to pull
 multiple branches into the same local repository, and then there is the
 option to pull the same branch into multiple local repositories. I don't
 think we need both.
 >
 Agreed.

 > What about just pulling all remote branches into the local repository?
 This should work well for all the repositories we use, and if and when
 there is a problem with this, we can think about remedying it, but we
 should not begin to design something around a problem that doesn't exist
 for us. That means there is a single local repository, and people can
 quickly switch (using git checkout).

 Agreed.

 >We would not have to handle lists of branches.
 What is the difficulty here? How GetComponents would checkout the
 different branch names without knowing their names in advance? Does the
 --mirror command do this job? why not let the user specify this list in
 the CRL file? It seems much easier to me and it is part of the repository
 information anyway.

-- 
Ticket URL: <https://trac.einsteintoolkit.org/ticket/248#comment:13>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit