Hello Hans, 2014-08-07 14:30 GMT+04:00 Hans Ulli Kroll <[email protected]>: > On Tue, 5 Aug 2014, Sergey Ryazanov wrote: > >> 2014-08-05 0:59 GMT+04:00 Felix Fietkau <[email protected]>: >> > On 2014-08-04 22:40, Sergey Ryazanov wrote: >> >> A humble request to the committers: use "svn cp" for patches and config >> >> file >> >> in order to preserve the history of changes. >> > I used git-svn, it has rename detection and handles this automatically. >> > >> Thanks a lot! >> >> -- >> BR, >> Sergey > > Hello > > I need some kind of a hint ... > > I'm currently working on getting kernel version 3.14 on ar71xx. > Tests on Hornet UB are working quite well and on WNDR3700v2 too. > > So this patchset is almost reasdy to submit. > But I will remain the history changes. > "svn cp" will not work, because of a true git repo. -> git clone > and "git-svn cp" is not available. > > Any leads ? > Git doesn't do copy tracking, but can do copy detect. More details here [1].
Many things depend on what do you mean when you say "remain the history changes". If you need to see history inside git repository, you could use "git log --follow <filename>". If you would like to reduce patch size, you could use "git format-patch --find-copies-harder". And as Felix said, git-svn automatically does a rename detection when sends changes to svn repository, if you plan to push your changes to svn repo. 1. http://stackoverflow.com/questions/1043388/record-file-copy-operation-with-git -- BR, Sergey _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
