We have a ton of fcrepo branches, most of which I'm reasonably certain can be 
pruned.

Aside from master, the list comprises (I've put names against branches per JIRA 
assignee). Branches with stars are ones I that I'm reasonably certain should be 
deleted.

Can you please review your branches and prune what's not needed? FYI:

        git branch -d <branch-name> (to delete your local branch)
        git push origin :<branch-name> (to delete the remote)

Thanks!

Adam
  origin/fcrepo-893
  origin/fcrepo-1061
  origin/fcrepo-1067
  origin/fcrepo-1084
  origin/fcrepo-1086 *

Asger
  origin/fcrepo-182
  origin/fcrepo-452 *
  origin/fcrepo-1041 *

Ben
  origin/fcrepo-787 *
  origin/fcrepo-787-clean *
  origin/fcrepo-850 *
  origin/fcrepo-944 *
  origin/fcrepo-1085
  origin/fcrepo-1109

Chris
  origin/fcrepo-748
  origin/fcrepo-946 *
  origin/fcrepo-1047

Frank
  origin/fcrepo-1023
  origin/fcrepo-1058

Steve
  origin/fcrepo-576 *
  origin/fcrepo-702 *
  origin/fcrepo-724
  origin/fcrepo-770
  origin/fcrepo-839 *
  origin/fcrepo-840 *
  origin/fcrepo-840-steve *
  origin/fcrepo-866 *
  origin/fcrepo-902 *
  origin/fcrepo-909 *
  origin/fcrepo-932 *
  origin/fcrepo-939 *
  origin/fcrepo-990
  origin/fcrepo-1020 *
  origin/fcrepo-1026 *

Unassigned
  origin/fcrepo-604 (Chris?)
  origin/fcrepo-644 (Ben?)
  origin/fcrepo-775 (Steve/Chris?)
  origin/fcrepo-795 * (Ben?)
  origin/fcrepo-940 (Chris?)
  origin/fesl-spring
  origin/maintenance-3.4
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fedora-commons-developers mailing list
Fedora-commons-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers

Reply via email to