On Sun, 5 Mar 2017 19:49:30 +
klaatu la terible wrote:
> I can't help but ask, what's the deciding factor on who gets a
> branch? I'd love to be able to update my builds with git.
I missed this before - send me a pubkey and desired username.
-RW
pgppH5R4TTLW7.pgp
Description: OpenPGP dig
* On 2017 07 Apr 20:25 -0500, Willy Sudiarto Raharjo wrote:
> Nevermind, i just merged your PR
Thanks, Willy.
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Ham radio, Linux, bikes, and more: http://www.n0nb.us
signatu
>> Perhaps this is where I erred. I created the standard GitHub pull
>> request to update development/astyle. I guess I need to post the branch
>> URL to this list?
>
> yes, otherwise, how do we know your github URL? :)
Nevermind, i just merged your PR
thanks
--
Willy Sudiarto Raharjo
si
>> you can send the URL of your branch to us and we can review them
>
> Perhaps this is where I erred. I created the standard GitHub pull
> request to update development/astyle. I guess I need to post the branch
> URL to this list?
yes, otherwise, how do we know your github URL? :)
--
Willy S
* On 2017 06 Mar 00:34 -0600, Willy Sudiarto Raharjo wrote:
> it's better to fork from https://github.com/SlackBuildsOrg/slackbuilds/
> and then create your own branch and start making changes
>
> Some notes:
> - always rebase from latest master branch
> - Only 1 commit per script
> - Use the foll
* On 2017 06 Mar 21:37 -0600, Willy Sudiarto Raharjo wrote:
> we (admins) do that automatically by using git hooks i sent earlier.
> That will automatically add SoB line everytime we merged other
> maintainer's work during public update.
>
> Maintainers can also use the git hooks for their reposi
> After browsing the recent commits, I noticed that each contains a
> "Signed-off-by: " line. In some cases it is signed by commit the author
> and in other cases I see that you (Willy) have signed it.
>
> I presume that this pattern indicates that a maintainer making a commit
> in their branch f
Hi Willy.
After browsing the recent commits, I noticed that each contains a
"Signed-off-by: " line. In some cases it is signed by commit the author
and in other cases I see that you (Willy) have signed it.
I presume that this pattern indicates that a maintainer making a commit
in their branch fo
I just wanted to add my input, for whatever it is worth, that one of the
chief things I find attractive about SBo is the"maintainer model". That
is not to say Sbo's utilization of this model cannot be improved;
because, I think it can be. Overall I think, things should remain much
the same as they
>> We only support git. cgit is just web interface so can see other's work
>
> I upload my SlackBuilds to GitHub
> (https://github.com/drgibbon/slackbuilds), is there any way for that to
> be incorporated into the workflow? I find making a tar archive/uploading
> to the website to be quite unwield
On 03/06/2017 02:22 AM, Willy Sudiarto Raharjo wrote:
>> Do you prefer one method over another?
>
> We only support git. cgit is just web interface so can see other's work
I upload my SlackBuilds to GitHub
(https://github.com/drgibbon/slackbuilds), is there any way for that to
be incorporated int
On Sun, Mar 05, 2017 at 11:24:34PM +0700, Willy Sudiarto Raharjo wrote:
> > For the moment SBo prefers tarballs, well, for the moment that's the
> > only option.
> >
> > There is no git for ordinary users and maintainers as of now.
>
> That's not true
> we do allow "some" maintainers to have thei
> I am pretty sure that this, more cvs/svn orientated branching strategy is
> not optimal.
>
> There is no need for users to have branches, they should have forks.
> There they can branch, and create for these branches pull requests.
>
> Of course you can create also branches per user, but this o
>> You could take pull requests from every trust able person fore each package,
>> the maintainer models is total obsolete that only scales bad, distributes
>> work bad, and is a bottleneck by design.
>
> Who, or what, is going to do the required testing?
Well, I agree with David. I think the m
> There is no need for users to have branches, they should have forks.
> There they can branch, and create for these branches pull requests.
We do have the vague intention of using Gitlab like that, but it is an
ongoing research project, because first we need an answer to the
question below:
> Yo
I am pretty sure that this, more cvs/svn orientated branching strategy is
not optimal.
There is no need for users to have branches, they should have forks.
There they can branch, and create for these branches pull requests.
Of course you can create also branches per user, but this only pollutes t
> For the moment SBo prefers tarballs, well, for the moment that's the
> only option.
>
> There is no git for ordinary users and maintainers as of now.
That's not true
we do allow "some" maintainers to have their own branches in our GIT
repository. See https://slackbuilds.org/cgit/slackbuilds/
> Do you prefer one method over another?
We only support git. cgit is just web interface so can see other's work
--
Willy Sudiarto Raharjo
signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@sla
On 05/03/17 15:38, Jeremy Hansen wrote:
On Sun, Mar 5, 2017, 3:10 AM Willy Sudiarto Raharjo
mailto:will...@slackbuilds.org>> wrote:
> I've always wondered about this. Wouldn't it be easier for the
> maintenance team to deal with _some_ form of version control, rather
> than updated
On Sun, Mar 5, 2017, 3:10 AM Willy Sudiarto Raharjo
wrote:
> > I've always wondered about this. Wouldn't it be easier for the
> > maintenance team to deal with _some_ form of version control, rather
> > than updated archives delivered through slackbuilds.org?
>
> We do have and we used git
>
> se
> I've always wondered about this. Wouldn't it be easier for the
> maintenance team to deal with _some_ form of version control, rather
> than updated archives delivered through slackbuilds.org?
We do have and we used git
see the web-based interface here:
https://slackbuilds.org/cgit/slackbuilds
On 03/05/2017 04:38 AM, Willy Sudiarto Raharjo wrote:
>>> is there a guide or any sort of documentation about how to submit
>>> patches to slackbuilds.org via git?
>>
>> I think it's not supported.
>
> Not officially supported, but i personally have accepted PR from public
> github repository fo
>> is there a guide or any sort of documentation about how to submit
>> patches to slackbuilds.org via git?
>
> I think it's not supported.
Not officially supported, but i personally have accepted PR from public
github repository for some people for their own scripts (not updating
others nor ne
On 04/03/17 14:41, Nikos Giotis wrote:
is there a guide or any sort of documentation about how to submit
patches to slackbuilds.org via git?
I think it's not supported.
--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBui
Hi,
is there a guide or any sort of documentation about how to submit
patches to slackbuilds.org via git?
Nikos
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archiv
25 matches
Mail list logo
