On Tue, 2016-02-16 at 17:36 +0100, Lukas Slebodnik wrote:
> On (12/01/16 14:11), Lukas Slebodnik wrote:
> >On (12/01/16 13:40), Lukas Slebodnik wrote:
> >>On (05/11/15 13:51), Sumit Bose wrote:
> >>>On Thu, Nov 05, 2015 at 01:02:07PM +0100, Lukas Slebodnik wrote:
> On (05/11/15 12:42), Sumit B
On (12/01/16 14:11), Lukas Slebodnik wrote:
>On (12/01/16 13:40), Lukas Slebodnik wrote:
>>On (05/11/15 13:51), Sumit Bose wrote:
>>>On Thu, Nov 05, 2015 at 01:02:07PM +0100, Lukas Slebodnik wrote:
On (05/11/15 12:42), Sumit Bose wrote:
>On Thu, Nov 05, 2015 at 12:12:17PM +0100, Lukas Sle
On (16/02/16 11:03), Jakub Hrozek wrote:
>On Tue, Feb 16, 2016 at 10:58:35AM +0100, Pavel Březina wrote:
>> On 02/16/2016 10:55 AM, Jakub Hrozek wrote:
>> >see subject, I would like to add:
>> > - how to debug:
>> > - summarize what to look for if the feature does not work. It's
>> >
On (15/02/16 18:27), Lukas Slebodnik wrote:
>On (15/02/16 18:20), Jakub Hrozek wrote:
>>On Fri, Aug 14, 2015 at 11:00:25PM +0200, Jakub Hrozek wrote:
>>> On Thu, Aug 13, 2015 at 05:17:32PM +0200, Jakub Hrozek wrote:
>>> > ACK
>>> >
>>> > I'll just wait for CI results before pushing.
>>>
>>> * mas
On (15/02/16 18:30), Jakub Hrozek wrote:
>On Mon, Feb 15, 2016 at 01:59:27PM +0100, Lukas Slebodnik wrote:
>> On (10/02/16 10:31), Lukas Slebodnik wrote:
>> >On (04/02/16 16:22), Jakub Hrozek wrote:
>> >>On Thu, Feb 04, 2016 at 03:52:35PM +0100, Jakub Hrozek wrote:
>> >>> On Tue, Feb 02, 2016 at 04
Hi,
I prepared the release notes for the 1.11.8 release here:
https://fedorahosted.org/sssd/wiki/Releases/Notes-1.11.8
Please comment or edit..
___
sssd-devel mailing list
sssd-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/
On Tue, Feb 16, 2016 at 10:58:35AM +0100, Pavel Březina wrote:
> On 02/16/2016 10:55 AM, Jakub Hrozek wrote:
> >see subject, I would like to add:
> > - how to debug:
> > - summarize what to look for if the feature does not work. It's
> > fine to say something like 'follow gene
On 02/16/2016 10:55 AM, Jakub Hrozek wrote:
see subject, I would like to add:
- how to debug:
- summarize what to look for if the feature does not work. It's
fine to say something like 'follow generic sssd debugging
procedure' but we should think about debug me
see subject, I would like to add:
- how to debug:
- summarize what to look for if the feature does not work. It's
fine to say something like 'follow generic sssd debugging
procedure' but we should think about debug messages and the
debugging process when we
