Here I totally agree with Till and usually I'm doing the same (it doesn't
happen often, but anyway).
Because I also not available day to day. For example today I have time and
next time I will have time like month..
Just wanted to share my opinion.
On Mon, Feb 15, 2016, 7:23 PM Josh Boyer wrote
On Mon, Feb 15, 2016 at 12:20 PM, Till Maas wrote:
> On Mon, Feb 15, 2016 at 07:47:08AM -0500, Josh Boyer wrote:
>
>> You misunderstand. I was not suggesting you ask for permission. I
>> was stating that IRC contact alone, for whatever reason, is not
>> necessarily sufficient as an attempt to co
On Mon, Feb 15, 2016 at 07:47:08AM -0500, Josh Boyer wrote:
> You misunderstand. I was not suggesting you ask for permission. I
> was stating that IRC contact alone, for whatever reason, is not
> necessarily sufficient as an attempt to contact a maintainer. You can
> convey _much_ more informat
Hi,
On 15-02-16 14:15, Josh Boyer wrote:
On Mon, Feb 15, 2016 at 7:57 AM, Hans de Goede wrote:
Hi,
On 15-02-16 13:47, Josh Boyer wrote:
While I'm still very much on the fence about this, moving to pagure
for dist-git might very much help in these situations. Being able to
send a pull req
>>> > While I'm still very much on the fence about this, moving to pagure
>>> > for dist-git might very much help in these situations. Being able
>>> > to send a pull request with your changes easily means you've fixed
>>> > it, the maintainer just needs to pull it in. All of the
>>> > informatio
On 15/02/16 13:57 +0100, Hans de Goede wrote:
Hi,
On 15-02-16 13:47, Josh Boyer wrote:
While I'm still very much on the fence about this, moving to pagure
for dist-git might very much help in these situations. Being able to
send a pull request with your changes easily means you've fixed it,
On Mon, Feb 15, 2016 at 8:09 AM, Dan Horák wrote:
> On Mon, 15 Feb 2016 13:57:39 +0100
> Hans de Goede wrote:
>
>> Hi,
>>
>> On 15-02-16 13:47, Josh Boyer wrote:
>>
>>
>>
>> > While I'm still very much on the fence about this, moving to pagure
>> > for dist-git might very much help in these situ
On Mon, Feb 15, 2016 at 7:57 AM, Hans de Goede wrote:
> Hi,
>
> On 15-02-16 13:47, Josh Boyer wrote:
>
>
>
>> While I'm still very much on the fence about this, moving to pagure
>> for dist-git might very much help in these situations. Being able to
>> send a pull request with your changes easil
On Mon, 15 Feb 2016 13:57:39 +0100
Hans de Goede wrote:
> Hi,
>
> On 15-02-16 13:47, Josh Boyer wrote:
>
>
>
> > While I'm still very much on the fence about this, moving to pagure
> > for dist-git might very much help in these situations. Being able
> > to send a pull request with your chan
Hi,
On 15-02-16 13:47, Josh Boyer wrote:
While I'm still very much on the fence about this, moving to pagure
for dist-git might very much help in these situations. Being able to
send a pull request with your changes easily means you've fixed it,
the maintainer just needs to pull it in. All
On Sun, Feb 14, 2016 at 2:32 PM, Till Maas wrote:
> On Sat, Feb 13, 2016 at 04:29:38PM -0500, Josh Boyer wrote:
>
>> I'm not going to weigh in on the changes, but I did want to address
>> this in public so others can learn.
>
> IMHO the kind of changes are important here. The situation was that
>
- Original Message -
> From: "Josh Boyer"
> To: "Development discussions related to Fedora"
>
> Sent: Saturday, February 13, 2016 10:29:38 PM
> Subject: Re: Please stop modifying other people's packages without
> coordinating with them
On Sun, Feb 14, 2016 at 08:50:34PM +0100, Till Maas wrote:
> On Sat, Feb 13, 2016 at 05:40:07PM -0800, Alex Gagniuc wrote:
> > yes, I have an IRC bouncer server, so I was able to find your question
> > after some grepping. It was posted before dawn in my timezone, so I
> > wouldn't have had a chan
On Sat, Feb 13, 2016 at 05:40:07PM -0800, Alex Gagniuc wrote:
> On Sat, Feb 13, 2016 at 9:57 AM, Till Maas
> wrote:
> # Zero-day patches after 0.3.0 release. Extract using:
> # $ git clone git://sigrok.org/pulseview.git
> # $ cd pulseview
> # $ git checkout a1a3656b4e18cb9fc078a51bf4256066ee30762
On Sat, Feb 13, 2016 at 04:29:38PM -0500, Josh Boyer wrote:
> I'm not going to weigh in on the changes, but I did want to address
> this in public so others can learn.
IMHO the kind of changes are important here. The situation was that
there were was an incomplete update to the sigrok packages in
On Sat, Feb 13, 2016 at 9:57 AM, Till Maas wrote:
> Hi Alex,
Hi Till,
> the changes were not unrelated but fixed the build error for pulseview
> on Rawhide and extending the build overrides fixed the build errors on
> F23 (which you can also read in the changelog).
I noticed the changes were ze
On Sat, Feb 13, 2016 at 12:57 PM, Till Maas wrote:
> Hi Alex,
>
> On Sa, Feb 13, 2016 at 09:43:06 -0800, Alex Gagniuc wrote:
>
>> I was in the process of upgrading to the latest upstream releases,
>> which came out about a week ago. You've interrupted the process by
>> pushing some unrelated chang
Hi Alex,
On Sa, Feb 13, 2016 at 09:43:06 -0800, Alex Gagniuc wrote:
> I was in the process of upgrading to the latest upstream releases,
> which came out about a week ago. You've interrupted the process by
> pushing some unrelated changes, and now I have to figure out what
the changes were not u
18 matches
Mail list logo
