[petsc-dev] git repo branches housekeeping

Lisandro Dalcin dalcinl at gmail.com
Mon Apr 1 03:24:43 CDT 2019


On Fri, 29 Mar 2019 at 19:22, Balay, Satish via petsc-dev <
petsc-dev at mcs.anl.gov> wrote:

> ref: https://lists.mcs.anl.gov/pipermail/petsc-dev/2018-April/022748.html
>
> I've deleted all development branches that are already merged into
> maint (v3.11) from https://bitbucket.org/petsc/petsc
>
>
Would it make sense to make this cleanup in a regular basis? Once a PR is
merged into master, what's the point of keeping the branch around until
next release? It makes it heavier to search for a branch in Bitbucket, "git
remote show origin" produces huge listing.
I try hard myself of remembering to remove my merged branches, or select
"close source branch" when I make the PR.

PS: Follow @shitbsmithsays advice and flush the toilet!

-- 
Lisandro Dalcin
============
Research Scientist
Extreme Computing Research Center (ECRC)
King Abdullah University of Science and Technology (KAUST)
http://ecrc.kaust.edu.sa/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20190401/7c6f3456/attachment.html>


More information about the petsc-dev mailing list