sPHENIX tracking discussion

["Frawley, Anthony" <afrawley AT fsu.edu>]

That is excellent news Martin! Thanks a lot!

Tony

---

From: sphenix-tracking-l-bounces AT lists.bnl.gov [sphenix-tracking-l-bounces AT lists.bnl.gov] on behalf of Michael P. McCumber [mccumber AT bnl.gov]
Sent: Friday, October 23, 2015 3:29 PM
To: Martin Purschke
Cc: sphenix-tracking-l AT lists.bnl.gov
Subject: Re: [Sphenix-tracking-l] recovering "lost" overleaf text

Thanks! This seems tex also contains my missing text too.

Mike

--

Michael P. McCumber, PhD
Los Alamos National Laboratory
505-709-8161

On Fri, Oct 23, 2015 at 1:22 PM, Martin Purschke <purschke AT bnl.gov> wrote:

All, especially Tom, Mike, and Tony,

there are numerous complaints that files are easily getting overwritten
in overleaf, which seems to be some race condition between the web
interface and the overleaf git export.

Luckily, whenever something gets committed to the git repo, it leaves a
trace. Tom was looking for some text about MAPS that he had written that
disappeared in a subsequent commit. It dos NOT take a tag or so to make
those past changes accessible later.

If you issue the command "git log" to see what has been going on, you get

> commit cb314d8c288d323e4f8c3af8456bf13567b97a48
> Author: John Lajoie <lajoie AT iastate.edu>
> Date:   Thu Oct 15 21:02:59 2015 +0000
>
>     Update on Overleaf.
>
> commit 5695f8e278643261fe4a001e27bf57898861257d
> Author: Thomas Hemmick <tkhemmick AT gmail.com>
> Date:   Thu Oct 15 20:40:15 2015 +0000
>
>     Update on Overleaf.
>
> commit de69855348560a869455de1eefc510e6933783bf
> Author: Thomas Hemmick <tkhemmick AT gmail.com>
> Date:   Thu Oct 15 20:38:25 2015 +0000
>
>     Update on Overleaf.
>
> commit daf86ed149bd2aa5315c6c45d269999428ba196a
> Author: Jin Huang <blackcathj AT gmail.com>
> Date:   Thu Oct 15 18:14:46 2015 +0000
>
>     Update on Overleaf.
...

and so on.

Tom advised that the text in question, now gone, contained the string
"latch up". I made a list of all commits with those long hex codes

> git log | grep commit | awk '{print $NF}'  > commits

and then went through them one by one to see when the string would appear.

> $ cat search_latchup.sh
> #! /bin/sh
>
> git checkout master > /dev/null 2>&1
>
> for c in $(cat commits) ; do
>
>     echo $c
>     git checkout $c  > /dev/null 2>&1
>     if grep -iq 'latch up' tracker/tracker.tex ; then
>       echo -n "$c  "
>       grep -i 'latch up' tracker/tracker.tex
>     fi
>     git checkout -f master > /dev/null 2>&1
> done

Lo and behold, in this case, cb314d8c288d323e4f8c3af8456bf13567b97a48 is
the one. For Tom's benefit, I attach the corresponding tracker.tex
version, but now you have the recipe.

Best,
        Martin

--
Martin L. Purschke, Ph.D.        ;   purschke AT bnl.gov
                                 ;   http://www.phenix.bnl.gov/~purschke
                                 ;
Brookhaven National Laboratory   ;   phone: +1-631-344-5244
Physics Department Bldg 510 C    ;   fax:   +1-631-344-3253
Upton, NY 11973-5000             ;   skype: mpurschke
-----------------------------------------------------------------------

_______________________________________________
Sphenix-tracking-l mailing list
Sphenix-tracking-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/sphenix-tracking-l