2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | AW: another git question |
From: | "Zimoch Dirk \(PSI\) via Core-talk" <core-talk at aps.anl.gov> |
To: | "Yendell, Gary (DLSLtd,RAL,LSCI)" <gary.yendell at diamond.ac.uk> |
Cc: | "core-talk at aps.anl.gov" <core-talk at aps.anl.gov> |
Date: | Fri, 20 Nov 2020 09:09:20 +0000 |
Hello Gary, Thanks for the suggestion. But I doubt that I can easily undo the whole "let's move the whole libCom directory into a completely different location" which had been done for EPICS 7. I do not understand why git claims that the file had been deleted instead of moved. Is this how the move had been done? Delete eveything and then add everything again? It seems so as 'git log modules/libcom/src/osi/os/posix/osdMutex.c'
staryts with commit 833648c97762c404bd44f1eddf9174cdd396dcc4 Author: Ralph Lange <ralph.lange at gmx.de> Date: Tue Jun 19 11:24:03 2018 +0200 Move all under modules/libcom No history from before the move. It seems that git has no idea that EPICS 7 modules/libcom/src/osi/os/posix/osdMutex.c has anything to do with EPICS 3 src/libCom/osi/os/posix/osdMutex.c Another problem was that the commit contained files in libCom _and_ a file in configure so that not all paths changed the same way. I have now applied all changes manually for each individual file. I had to modify several things anyway because of changes from EPICS 3 to 7. Cheers, Dirk Von: Yendell, Gary (DLSLtd,RAL,LSCI) <gary.yendell at diamond.ac.uk>
Hi Dirk, You may want to play around with the find renames option on the cherry-pick commands [1]. This adjusts the allowed % difference between two files for them to be considered
renamed, rather than deleted and created. If that doesn't work, you could
Possibly this could be scripted if it is the only thing that works and you need to do it frequently. (Apologies if this email doesn't come through properly, I am only subscribed to core talk by RSS, so I didn't have an email to reply to.) Cheers, Gary -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt
by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. |