On Sat, 4 Jan 2025 at 17:11, Elliotte Rusty Harold <elh...@ibiblio.org> wrote:
>
> The tail is wagging the dog here. It sounds like you need to
> reconfigure the mailing list to not be so noisy; i.e. to ignore
> commits on non-master branches. The problem is the mailing list, not
> the branches.

It will be difficult to say which branches should be notified by ML
and which should not be ... so all branches generate notifications.

>
> On Sat, Jan 4, 2025 at 2:46 PM Tamás Cservenák <ta...@cservenak.net> wrote:
> >
> > >>> and shouldn't clutter the commit logs.
> >
> > Well, my point is that they DO clutter commit logs, see ML link.
> >
> > On your (private) fork I am not notified about your each commit, while
> > I AM notified about each commit on ASF repo :)
> >
> > Also, I DO want to be notified about ANY change happening in canonical
> > ASF reposes, so IMHO this is not a "red herring".
> > Just use a fork, that's all.
> >
> > Thanks
> > T
> >
> > On Sat, Jan 4, 2025 at 3:26 PM Elliotte Rusty Harold <elh...@ibiblio.org> 
> > wrote:
> > >
> > > This shouldn't be a problem if we disable everything except squash and
> > > merge and require all commits to go through PRs. We do have a big
> > > problem with commits that go straight into the source tree without a
> > > PR or a code review.
> > >
> > > Branch vs fork is a red herring. IMHO working on branches is much
> > > simpler and shouldn't clutter the commit logs.
> > >
> > > On Sat, Jan 4, 2025 at 2:15 PM Tamás Cservenák <ta...@cservenak.net> 
> > > wrote:
> > > >
> > > > Howdy,
> > > >
> > > > I'd like to ask devs to NOT code directly against branches in ASF
> > > > repositories, as we are swamped literally with unwanted spam: I am not
> > > > interested in each commit of the branch being worked on.
> > > >
> > > > Instead, fork the repo and create PRs.
> > > >
> > > > The commits ML is nearly unusable, I'd really like to see _only the
> > > > changes_ in "proper" codebases, but instead we have thousands of mails
> > > > about commits on any branch in there:
> > > > https://lists.apache.org/list.html?comm...@maven.apache.org
> > > >
> > > > This also raises the problem of branch cleanup in canonical reposes as 
> > > > well...
> > > >
> > > > TL;DR: fork and create PRs from forks please.
> > > >
> > > > Thanks,
> > > > T
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > >
> > >
> > >
> > > --
> > > 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
> >
>
>
> --
> 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
>


-- 
Sławomir Jaranowski

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to