Eliotte, don't get me wrong, but i have hard time to follow your reasoning: - i posted how we all are _swamped_ by commit mails as canonical repo is used for development - you came back as "ML is misconfigured" - then I asked you who will clean up these vaguely named branches you create in canonical repo - you came back with "branches as cheap" and "eventually project will move off git" and "branches are how git works"?
WAT? Thanks T On Sat, Jan 4, 2025 at 7:02 PM Elliotte Rusty Harold <elh...@ibiblio.org> wrote: > > On Sat, Jan 4, 2025 at 4:20 PM Tamás Cservenák <ta...@cservenak.net> wrote: > > > > > But to continue: what will happen to branches named like "mdo", > > "apidoc", "copy", "null" etc in _cnonical maven repo_ if you go > > missing? > > Branches are cheap, but the way these things work if these aren't > cleaned up manually, eventually the project will move off git and > github and throw away its history. All this has happened before, and > all this will happen again . > > I've worked on enough Github hosted projects where all committers use > branches and only branches to be reasonably confident that the problem > is not the use of branches. Branches are how git works, and they work > just fine. Maven does seem to have a lot of old tooling that needs > work, though I'm not sure who has the knowledge or permissions to do > that. But meanwhile adding more layers of rules for developers to > follow instead of fixing broken tooling — like apparently whatever is > sending commit messages to the mailing list — is not the way to go. > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
