[Dune-devel] Git best practice: Remove merged branches

Christian Engwer christian.engwer at uni-muenster.de
Sun Oct 5 17:00:35 CEST 2014


I fully agree with this proposal.

Either you go ahead, or, if you want more backup, open a doodle.

Christian

On Thu, Oct 02, 2014 at 04:23:32PM +0200, Christoph Grüninger wrote:
> Hi fellow Dune developers,
> as we use more and more feature branches, the number of merged, but not
> deleted branches is rapidly growing.
> 
> So I propose to introduce the best practice for Git, to delete branches
> after a merge. Additionally, all merged but not deleted branch should be
> allowed to be deleted by anybody. Git helps identifying these:
> git branch -a --merged
> 
> By the way, I started the wiki page with the Git pest practices as we
> decided in Berlin:
> http://users.dune-project.org/projects/main-wiki/wiki/Git_best_practices
> 
> Bye
> Christoph
> 
> -- 
> GDB does hate your application, expresses its contempt through the
> design of its command-line interface.   -- Tom Tromey, FOSDEM 2014
> 



> _______________________________________________
> Dune-devel mailing list
> Dune-devel at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-devel


-- 
Prof. Dr. Christian Engwer 
Institut für Numerische und Angewandte Mathematik
Fachbereich Mathematik und Informatik der Universität Münster
Einsteinstrasse 62
48149 Münster

E-Mail	christian.engwer at uni-muenster.de
Telefon	+49 251 83-35067
FAX		+49 251 83-32729




More information about the Dune-devel mailing list