[Slackbuilds-users] template idea: --no-same-owner

[Duncan Roe]

Hi Willy,

On Tue, Aug 18, 2026 at 08:29:05PM +0700, Willy Sudiarto Raharjo wrote:
> >        If the  git history  is inevitably  going to
> >  have thousands  of commits changing  little script
> >  compliance  things, then  I would  suggest they're
> >  all made in one go.  Instead of having hundreds of
> >  noise commits in little chunks clustered over many
> >  months,  we'd just  have  them all  in one  chunk,
> >  where someone can skip  over them when reading the
> >  history.  Pushing  thousands of commits in  one go
> >  is not an issue for git, in my experience.  Unless
> >  you have an expensive  automation system that will
> >  have to run once for each commit, of course.
>
>
> This kind of situation is fine during development cycle, not during normal
> cycle where each commits will be listed in /ready and used as reference to know
> which script need to be updated and tarball creations during public update.
>
> In development cycle, all hell breaks loose :)
> You can add, remove, change, update, patch, anything
>
I'd prefer to do it that way too. But, as a non-admin, would I be able to?

If not, I see 2 alternatives:-

1. Make me an admin

2. I post the Q macros that do the job and an admin runs them.
   Needs the Q editor to be in the repo but it should be by then

In the meantime I'll finish testing the trickle system but won't start cron job,

Cheers ... Duncan.