Hi,
Le 02/08/2013 20:59, Derek Buitenhuis a écrit :
> As it stands right now, the grouping and wrapping of filenames
> in MinGW-w64's Makefiles makes tracking or viewing changes in
> version control very very hard, and makes it non-obvious what has
> changed.
>
> I propose that it move to a sorted, single-filename-per-line Makefile
> style, which will make additions/deletions/changes very easy to understand,
> and I volunteer to carry out the change if it is agreed upon.
>
> Comments, flames, or questions?
I would second that, I'm myself culprit of not realigning after the
removal/addition of a file to the build rules.
Since I spend quite a lot of time reading the code through git log in
form of patches (I know subversion users do not do it because svn is
very much less efficient for showing single changes), it would be
definitely better to have something like:
src_libmingwex = \
crt/dllentry.c \
crt/dllmain.c \
....
etc
With this change, patches would only show one single addition/deletion
per changed file, and be much more readable (Makefile.am would look
better as well IMHO)
> - Derek
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
