On 08/10/2016 04:49 PM, Chris Pavlina wrote:
[snip]
> Any particular reason for having (fixes lp:) in the first
> line? Typically the first line of the commit message is kept very
> short and limited to things one might need when quickly browsing a
> log. The usual convention in git is to
I can log in now.
On Wed, Aug 10, 2016 at 9:52 AM, Wayne Stambaugh
wrote:
>
>
> On 8/10/2016 11:52 AM, jp charras wrote:
> > Le 10/08/2016 à 17:28, Chris Pavlina a écrit :
> >> Same here, just wait a while. It's just being Launchpad.
> >
> > Or something else...
> > I have
On 8/10/2016 11:52 AM, jp charras wrote:
> Le 10/08/2016 à 17:28, Chris Pavlina a écrit :
>> Same here, just wait a while. It's just being Launchpad.
>
> Or something else...
> I have no problem.
Me neither but I was already logged.
>
>>
>> On Wed, Aug 10, 2016 at 11:26 AM, Duane Johnson
It was resolved quickly. Still, it was noticed independently by at
least three people, so def lp :)
On Wed, Aug 10, 2016 at 11:52 AM, jp charras wrote:
> Le 10/08/2016 à 17:28, Chris Pavlina a écrit :
>> Same here, just wait a while. It's just being Launchpad.
>
> Or
Le 10/08/2016 à 17:28, Chris Pavlina a écrit :
> Same here, just wait a while. It's just being Launchpad.
Or something else...
I have no problem.
>
> On Wed, Aug 10, 2016 at 11:26 AM, Duane Johnson
> wrote:
>> When I try to login at launchpad, I get a very long
Same here, just wait a while. It's just being Launchpad.
On Wed, Aug 10, 2016 at 11:26 AM, Duane Johnson wrote:
> When I try to login at launchpad, I get a very long "Waiting for
> launchpad.net" message followed by "OpenID Provider is Unavailable at This
> Time".
>
>
When I try to login at launchpad, I get a very long "Waiting for
launchpad.net" message followed by "OpenID Provider is Unavailable at This
Time".
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
Le 10/08/2016 à 16:36, Wayne Stambaugh a écrit :
> On 8/6/2016 11:03 AM, Thomas Pointhuber wrote:
>> Hy,
>>
>> as Library maintainer I got some insights about the various file formats and
>> as well their current
>> limits. Inspired by the current eeschema file format rework I would propose
>>
On Wed, Aug 10, 2016 at 9:34 AM, Wayne Stambaugh wrote:
>
> On 8/10/2016 5:02 AM, Maciej Sumiński wrote:
> > On 08/08/2016 06:09 PM, Wayne Stambaugh wrote:
> >> The last time I looked, notifications of repo commits still were not
> >> implemented. This is a show stopper for
On 8/6/2016 11:03 AM, Thomas Pointhuber wrote:
> Hy,
>
> as Library maintainer I got some insights about the various file formats and
> as well their current
> limits. Inspired by the current eeschema file format rework I would propose
> some changes for the
> footprint files as well.
>
>
>
Orson & Tom,
Please look over this patch when you get a chance to see if it makes
sense to commit it.
Thanks,
Wayne
On 8/6/2016 9:36 PM, Chris Pavlina wrote:
> The board I'm working on is quite complex and makes KiCad _very_ slow,
> so I'm working on a bit of profiling and optimizing. The
On 8/10/2016 5:02 AM, Maciej Sumiński wrote:
> On 08/08/2016 06:09 PM, Wayne Stambaugh wrote:
>> The last time I looked, notifications of repo commits still were not
>> implemented. This is a show stopper for me. I don't want to have to
>> constantly grep the git commit log to see what changed.
Le 10/08/2016 à 14:47, Maciej Sumiński a écrit :
> On 08/10/2016 02:43 PM, jp charras wrote:
>> Le 10/08/2016 à 10:21, jp charras a écrit :
>>> Le 10/08/2016 à 09:43, jp charras a écrit :
Le 10/08/2016 à 09:03, Maciej Sumiński a écrit :
> Hi Jean-Pierre,
>
> This is strange. I had
On 08/10/2016 02:43 PM, jp charras wrote:
> Le 10/08/2016 à 10:21, jp charras a écrit :
>> Le 10/08/2016 à 09:43, jp charras a écrit :
>>> Le 10/08/2016 à 09:03, Maciej Sumiński a écrit :
Hi Jean-Pierre,
This is strange. I had the problem you describe (Windows 7 x86_64) and
Le 10/08/2016 à 10:21, jp charras a écrit :
> Le 10/08/2016 à 09:43, jp charras a écrit :
>> Le 10/08/2016 à 09:03, Maciej Sumiński a écrit :
>>> Hi Jean-Pierre,
>>>
>>> This is strange. I had the problem you describe (Windows 7 x86_64) and
>>> fixed it in commit ee24275f [1].
>>> 1.
>>>
On 08/08/2016 06:09 PM, Wayne Stambaugh wrote:
> The last time I looked, notifications of repo commits still were not
> implemented. This is a show stopper for me. I don't want to have to
> constantly grep the git commit log to see what changed. If change
> notifications are working correctly,
Le 10/08/2016 à 09:43, jp charras a écrit :
> Le 10/08/2016 à 09:03, Maciej Sumiński a écrit :
>> Hi Jean-Pierre,
>>
>> This is strange. I had the problem you describe (Windows 7 x86_64) and
>> fixed it in commit ee24275f [1].
>> 1.
>>
Le 10/08/2016 à 09:03, Maciej Sumiński a écrit :
> Hi Jean-Pierre,
>
> This is strange. I had the problem you describe (Windows 7 x86_64) and
> fixed it in commit ee24275f [1]. Does the cursor look fine if you revert
> the commit? What wxWidgets & Windows versions do you use?
Yes, the cursor
Hi Jean-Pierre,
This is strange. I had the problem you describe (Windows 7 x86_64) and
fixed it in commit ee24275f [1]. Does the cursor look fine if you revert
the commit? What wxWidgets & Windows versions do you use?
Regards,
Orson
1.
19 matches
Mail list logo