This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Bug 1001187] New port - HAL: Freescale Kinetis variant,TWR-K60N512, TWR-K40X256 plf; Devs: Freescale UART and ENET (Ethernet)
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: unassigned at bugs dot ecos dot sourceware dot org
- Date: Thu, 27 Oct 2011 23:04:02 +0100
- Subject: [Bug 1001187] New port - HAL: Freescale Kinetis variant,TWR-K60N512, TWR-K40X256 plf; Devs: Freescale UART and ENET (Ethernet)
- Auto-submitted: auto-generated
- References: <bug-1001187-777@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001187
--- Comment #41 from Ilija Kocho <ilijak@siva.com.mk> 2011-10-27 23:03:56 BST ---
(In reply to comment #40)
> (In reply to comment #39)
> > Hi Sergei
>
> Hi Ilija,
>
> > > Ilija, if you will send some corrections, also, you would get rid
> > > the trailing whitespaces (mostly in CDL) and expand a few tabs in
> > > ethernet driver, also, I would get rid such shorthands
> > >
> > > }while(need_service);
> >
> > I hope all trailing whitespace is taken out and formating set.
>
> Even more than :-) A global search-n-replace (or script) did rid and
> white spaces in the eCos copyright headers. A few lines in my ~/.vimrc
> regarding 'BadWhitespace' made me too picky :-) But as much as they are
> highlighted in *red* I'm picking on them. Perhaps today this arraignment
> seem archaic and I'm thinking what I should comment them out (I mean my
> settings for $EDITOR).
>
So copyright banner has different rules...
I could adapt the clean macro in my editor for future.
What are the rules for whitespace?
> No need to re-send the patches, I'll raise those banners.
Tank you.
Ilija
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.