On Sun, 20 Dec 2015 16:42:47 +0100, aitor_czr wrote in message
<5676CC77.9030900@???>:

>
> Hi Arnt,
>
>
> On 12/20/2015 02:21 PM, Arnt Karlsen <arnt@???> wrote:
> > On Sun, 20 Dec 2015 13:02:28 +0100, aitor_czr wrote in message
> > <567698D4.1080901@???>:
> >
> >> >You can generate a patch in the parent directory by the following
> >> >way:
> >> >
> >> >$ git diff --relative > ../aitor_czr-20.2.2015.patch
> > ...or $ git diff --relative > ../aitor_czr-$(date +%FT%T-%Z).patch
> > oooooooooooooooooor ;o) $ git diff --relative > \
> > ../aitor_czr-$(git log |head -n1 |cut -d" " -f2)-$(date
> > +%FT%T-%Z).patch
>
>
> This generates a patch named:
>
> aitor_czr-2015-12-20T16:34:19-CET.patch
>
> ooooooooooooor ;o)
>
> aitor_czr-f1b0bdff4e61d3425ccdd425d2452c8b3c346df4-2015-12-20T16:12:25-CET.patch
>
> Here, $(git log |head -n1 |cut -d" " -f2) is the bizarre hash of 40
> digits content in:
>
> .git/refs/heads/master [*]
>
> Thanks,
>

>     Aitor.

>
> [*] This is being in the master branch.
>
>

..and if you reeeeeeeeeaaally wanna spell it out ;o) $ git diff \
--relative > ../aitor_czr-$(git log |head |tr [:space:] _ ).patch

--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.