octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #42513] io: Some temporary variables in PKG_AD


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #42513] io: Some temporary variables in PKG_ADD are not cleaned up
Date: Thu, 05 Jun 2014 17:12:44 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 Iceape/2.22

Update of bug #42513 (project octave):

                  Status:                    None => Patch Submitted        

    _______________________________________________________

Follow-up Comment #1:

What io package version?
Confirmed on my Linux box with io-2.2.2.  cs looks good to me. Thank you for
that + reporting.

As to the CRLF, I always clean them up manually (dos2unix) for all files (I
mostly develop on Windows) but I may have overlooked it this time. Sorry about
that.
That said, I often wonder where those CRLF EOLs come from anyway as TTBOMK
neither Octave nor notepad++ produce them (notepad++ is instructed to leave
EOLs as they are on all my boxes). I tried to hunt it down several times to no
avail; I do the actual packaging on MinGW (MSYS CLI) which is no suspect
either AFAIK.

As Carnë moved io over to mercurial (not quite my initiative) it'll be some
time before I can fix it - svn was a breeze for me but currently I simply lack
time to learn to properly manage mercurial at developer's level (contributing
I think I can manage). Ah and my mercurial (=Linux distro) seems outdated as
well.
Apart from this bug + the EOLs, the svn repo was ready for a 2.2.3 release
(needed for octave 3.9.0+).

It would be nice if you could run the PKG* files thru dos2unix and produce a
cs for that too- then maybe Carné can push all changesets.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?42513>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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