Re: Revised git related information in -v/-V output (and %Config)

On Jan 1, 2009, at 3:29 AM, demerphq wrote:

> 2009/1/1 Craig A. Berry <[email protected]>:
>>
>> Processing the .patch file in configure.com should not be a big  
>> deal.  We
>> already process it the old way when it just had the Perforce change  
>> number
>> in it, so we just need to update that to do what make_patchnum.sh  
>> does.
>
> So ill assume it shouldn't be too difficult. :-)

It's done, I think:

http://perl5.git.perl.org/perl.git/commit/9c3905ef054a16857454499c7acfa64d8373c309

We'll see how well that comes out in the wash as it was my first git  
push attempt.

>> Since there is also no generally available rsync on VMS, the only  
>> practical
>> way to stay current with blead is to generate your own snapshot on  
>> a system
>> that does have rsync and/or git.  If we haven't already done so, it  
>> would be
>> nice to document the recommended procedure for generating a  
>> snapshot.  I
>> assume it involves running make_patchnum.sh followed but some  
>> incantation of
>> git --archive.
>
> If its useful I will take that onto myself. Meaning i will put some
> effort into making .tar.gz snapshots available for you. Please let me
> know what else i can do to make things easier for the VMS people.
>
> I will also look into producting documentation how to do so.

Thanks.

________________________________________
Craig A. Berry
mailto:[email protected]

"... getting out of a sonnet is much more
  difficult than getting in."
                  Brad Leithauser