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: | Re: Patch file for Records which use consistent epics data types |
From: | Michael Davidsaver <[email protected]> |
To: | Jeong Han Lee <[email protected]> |
Cc: | [email protected] |
Date: | Thu, 27 Apr 2017 20:22:02 -0400 |
On 04/27/2017 07:50 PM, Jeong Han Lee wrote: > Hi Michael, > > I worked on the following epics-base : > > $git rev-parse HEAD > 8677c845283873895f39d81feca36cb24699e5ee Ok. As I think about it, now that we're using git. The git-format-patch command will give the base rev. commit message and diff together. > git format-patch -k -1 Does so for the most recent commit.