This is the mail archive of the
mailing list for the eCos project.
[Bug 1001569] Cortex-M arch. whitespace cleanup.
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: unassigned at bugs dot ecos dot sourceware dot org
- Date: Mon, 23 Apr 2012 17:51:53 +0100
- Subject: [Bug 1001569] Cortex-M arch. whitespace cleanup.
- Auto-submitted: auto-generated
- References: <email@example.com/>
Please do not reply to this email. Use the web interface provided at:
--- Comment #3 from Ilija Kocho <firstname.lastname@example.org> 2012-04-23 17:51:50 BST ---
(In reply to comment #2)
> I don't disagree with the principle and I have been looking forward to doing
> this sort of thing myself, but would you mind this being held back until we
> move to mercurial? Having these sweeping changes across many files is much
> easier to deal with, and less noisy, once we have a system which groups such
> changes into a single changeset.
This clean-up has a purpose and it is to make provision for clean patch(es)
that I intend to post soon. I don't know the prospective for switching to
mercurial but I'm afraid it won't be in time-frame that I need (surprise me :)
The alternatives for this patch (unless there is a pleasent surprise) are
either to merge the clean-up with contribution or post "dirty" patches which
IMO both will produce more noise than this patch.
I am aware that CVS keeps different version number for each file but the
proposed patch is limited to a single package (with single ChangeLog).
> There was a conversation before about fixing the trailing whitespace in
> copyright banners, and I suggested waiting before doing that for the same
> reason. At that point, we could probably remove all trailing whitespace from
> the entire repo (excepting any binary files), not just cortex-m.
Having that in mind I have left them intact.
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.