On 22 January 2013 15:37, CeDeROM <[email protected]> wrote: > On Tue, Jan 22, 2013 at 4:19 PM, Freddie Chopin <[email protected]> wrote: >> If you're refering to the patches that changed some debug outputs, renamed >> files or changed some comments in the places that were affected by one of >> your previous changes I also think it's good to have them merged. It would >> not be a blocker for me, but I don't mind that being squshed... What's the >> value of adding file abc.c and renaming it to def.c 3 changes later? Why not >> have def.c from the beginning, with complete history, without any renames? > > Simply, because we will erase history that way :-) This is true that > at the end everything will look the same, but we will have a history > of changes and as an example why I did resigned from the long file > names in favor of better directory structure and function/variables > naming convention :-) I have been working on this for months, I know > this may not look obvious at first glance :-) >
This is quite normal in git to have a dev history and to squash before merging to mainline. Spen ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
