gnucap-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnucap-devel] bugfix-WIP branch


From: Joakim Nilsson
Subject: Re: [Gnucap-devel] bugfix-WIP branch
Date: Sun, 13 Jul 2014 22:31:08 +0200

I just realised, I am replying to the wrong thread (not even the
correct mailing list). I'm sorry for spamming.

Regards,
Joakim

On Sun, Jul 13, 2014 at 10:28 PM, Joakim Nilsson <address@hidden> wrote:
> Thank you, Felix!
> Now on commit c6e4bee952affcaa4593e7e1de5e04b9c3e03620 as suggested, I
> tried the same thing as initially and the result is the same. The
> return status of gnucap is 0 even though there was an error. So, I
> suppose this is a bug?
>
> Here's the output:
>
> address@hidden:~/gnucap$ gnucap -b ../brokaw.ckt
> Gnucap : The Gnu Circuit Analysis Package
> Never trust any version less than 1.0
> Copyright 1982-2013, Albert Davis
> Gnucap comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome
> to redistribute it under the terms of
> the GNU General Public License, version 3 or later.
> See the file "COPYING" for details.
> main version: 2014-07-04 bugfix-WIP debug3
> core-lib version: 2014-07-04 bugfix-WIP debug3
> default plugins: 2014-07-04 bugfix-WIP debug3
> * Brokaw bandgap reference
> QNPN1: can't find: 1
> address@hidden:~/gnucap$ echo $?
> 0
>
> Also, maybe these emails should have gone to bug-gnucap instead...
>
> Regards,
> Joakim
>
> On Sun, Jul 13, 2014 at 8:11 PM, Felix Salfelder <address@hidden> wrote:
>> On Sun, Jul 13, 2014 at 07:48:38PM +0200, Joakim Nilsson wrote:
>>> [..] But I don't find 'bugfix-WIP'.
>>> Should it not be listed when I execute 'git branch -a' or do I
>>> misunderstand how git works?
>>
>> bugfix-WIP has been fast forward merged into master and then deleted.
>> this combination may lead to confusion indeed, if you're not fast
>> enough.
>>
>> one of these should improve the situation, and should be applied to
>> branches that have been mentioned on this list (next time).
>>
>> 1) branches remain alive after merge.
>> 2) merge branches with --no-ff and fill in a message.
>>
>> i think 2) is better and sufficient.
>>
>> cheers
>> felix
>>
>> PS: i think bugfix-WIP was c6e4bee952affcaa4593e7e1de5e04b9c3e03620 before it
>> was deleted.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]