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

[Willy Sudiarto Raharjo]

>        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 

--
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 870 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20260818/affa37f8/attachment.asc>