Git branch name to use for development branch based on release branch, not master

[Thomas Schwinge <thomas at codesourcery dot com>]

Hi!

Short version: OK to use Git branch name devel/omp/gcc-9 for what used to
be Subversion openacc-gcc-9-branch?


We used to have Subversion openacc-gcc-9-branch etc. branches: "for
collaborative development of OpenACC support and related functionality,
such as offloading support. The branch is based on gcc-9-branch."

First thing, going forward, we intend to rename the prefix from "openacc"
to "omp" so as to widen the development scope to also include OpenMP
etc.: "Offloading and Multi Processing".

Then, in the new Git world order, a direct translation would result in
Git branch name devel/omp-gcc-9 (without "branch" postfix; being based on
releases/gcc-9).  Would it maybe be better instead of hyphen-separated
devel/omp-gcc-9 to use slash-separated devel/gcc-9/omp (put "gcc-9"
first), or devel/omp/gcc-9 (put "omp" first)?

I don't care too much, but have a slight preference for devel/omp/gcc-9
(it keeps the short-hand "og9" tag meaningful, and devel/omp/gcc-10,
devel/omp/master, etc. group nicely), so suggest to use that going
forward, unless there is a request to not introduce any further
hierarchies (slash) in the devel/ namespace?


Grüße
 Thomas

Attachment: signature.asc
Description: PGP signature