On 19.10.2015 19:32, Christopher wrote:
> On Mon, Oct 19, 2015 at 9:42 AM Jared K. Smith
> wrote:
>
>> On Sun, Oct 18, 2015 at 3:37 PM, Marcin Zajączkowski wrote:
>>
>>> I like the idea with mirroring Fedora Git to GitHub. Read only mirror
>>> just to be a dedicated place for that kind of contri
On Mon, Oct 19, 2015 at 9:42 AM Jared K. Smith
wrote:
> On Sun, Oct 18, 2015 at 3:37 PM, Marcin Zajączkowski wrote:
>
>> I like the idea with mirroring Fedora Git to GitHub. Read only mirror
>> just to be a dedicated place for that kind of contributions (via pull
>> requests).
>>
>
> While I lik
On Mon, Oct 19, 2015 at 10:18:15AM -0400, Jeff Peeler wrote:
> On Sun, Oct 18, 2015 at 4:00 PM, Kevin Fenzi wrote:
> > I'd think a pagure.io like frontend would but at somewhat of a
> > different level than this. You would:
> >
> > * Go to the interface and create a fork of the package you want to
On Sun, Oct 18, 2015 at 4:00 PM, Kevin Fenzi wrote:
> I'd think a pagure.io like frontend would but at somewhat of a
> different level than this. You would:
>
> * Go to the interface and create a fork of the package you want to
> change.
> * Clone that fork and work on it locally with the normal
On Sun, Oct 18, 2015 at 3:37 PM, Marcin Zajączkowski wrote:
> I like the idea with mirroring Fedora Git to GitHub. Read only mirror
> just to be a dedicated place for that kind of contributions (via pull
> requests).
>
While I like the idea of making it easier for people to submit patches, I'm
n
On Sun, 18 Oct 2015 21:12:42 -0400
Neal Gompa wrote:
> Perhaps GitLab might be more appealing, since it is a FOSS service
> and it could be brought in-house relatively easily?
Not really.
There was an effort started I think in 2012 or 2013 to package it...
https://fedoraproject.org/wiki/Git
On 2015-10-19, Kevin Kofler wrote:
> 1. git clone …
> 2. commit your changes
> 3. git format-patch
> 4. attach to Bugzilla
>
The 3rd and 4th step can be simplified to "git send-bugzilla" command.
Although I think it can attach a patch only to already existing bug
report. This could be implemented
On Sun, Oct 18, 2015 at 3:37 PM, Marcin Zajączkowski wrote:
> Thanks for your responses, guys!
>
> On 2015-10-18 16:57, Christopher wrote:
> > To support this, I try to keep a mirror in GitHub for my packages... But
> > it's hard to stay in sync sometimes and nobody really knows it's there.
> > I
Marcin Zajączkowski wrote:
> I would like to propose a minor (yet important) change in one of the
> Fedora packages configuration (a SPEC file and/or a patch). Is it
> possible to create (something like) a pull request which could be
> reviewed by the maintainer in some convenient way (*) and optio
On Sun, 18 Oct 2015 21:41:41 +0200
Alec Leamas wrote:
> Perhaps OT, but I cannot resist: Have you discussed the overall
> workflow here? Cloning package, unpack sources, create patches, make
> a build, revise patches, finalize the spec, perhaps upstream to
> package owner...
Nope. As I said this
On 18/10/15 18:46, Kevin Fenzi wrote:
> On Sun, 18 Oct 2015 15:36:24 +0200
> Marcin Zajączkowski wrote:
>
>> Hi,
>>
>> I would like to propose a minor (yet important) change in one of the
>> Fedora packages configuration (a SPEC file and/or a patch). Is it
>> possible to create (something like) a
Thanks for your responses, guys!
On 2015-10-18 16:57, Christopher wrote:
> To support this, I try to keep a mirror in GitHub for my packages... But
> it's hard to stay in sync sometimes and nobody really knows it's there.
> It'd be nice if this were supported directly, perhaps by automatically
> m
On Sun, 18 Oct 2015 15:36:24 +0200
Marcin Zajączkowski wrote:
> Hi,
>
> I would like to propose a minor (yet important) change in one of the
> Fedora packages configuration (a SPEC file and/or a patch). Is it
> possible to create (something like) a pull request which could be
> reviewed by the m
On Sun, 2015-10-18 at 15:36 +0200, Marcin Zajączkowski wrote:
> Hi,
>
> I would like to propose a minor (yet important) change in one of the
> Fedora packages configuration (a SPEC file and/or a patch). Is it
> possible to create (something like) a pull request which could be
> reviewed by the mai
To support this, I try to keep a mirror in GitHub for my packages... But
it's hard to stay in sync sometimes and nobody really knows it's there.
It'd be nice if this were supported directly, perhaps by automatically
mirroring all packages in GitHub, like the ASF does, and emailing
maintainers when
Hi,
I would like to propose a minor (yet important) change in one of the
Fedora packages configuration (a SPEC file and/or a patch). Is it
possible to create (something like) a pull request which could be
reviewed by the maintainer in some convenient way (*) and optionally
merged? Or the only way
16 matches
Mail list logo
