A platform sed that is broken would be worked around by recognizing the platform. If the bulk of platforms are sane then fixing the path for the platform is the easiest solution. If the bulk of platforms don't have a sane sed then not using sed is probably the solution. If you want to make the path variable then a platform config file built automatically figuring out default paths that could be changed by the host's admin comes to mind (much like, oh I don't know, building a list of shell variables named author-script to use during rebases).
You could modify the name, email, and timestamp so they didn't have to be parsed. Separate lines in the header for name, email, and date would work. A length encoding of the three fields at the beginning of the header line or in some other (new) location if backwards compatibility is a concern. There's lots of rather straight-forward technical solutions.
Now if what you are saying is the social cost of applying any of those solutions is too high that's a horse of a different color.
Anyway thanks to everyone for the clue that got me working again,
-ljr
---
Lanny Ripple
lanny@xxxxxxxxxxxxxxxxx
On May 31, 2012, at 9:28 AM, Thomas Rast wrote:
> Lanny Ripple <lanny@xxxxxxxxxxxxxxxxx> writes:
>
>> Bingo.
>>
>> lanny;~> echo "Rémi Leblond" | LANG=C LC_ALL=C /usr/bin/sed -ne 's/.*/GIT_AUTHOR_NAME='\''&'\''/p'
>> GIT_AUTHOR_NAME='Rémi Leblond'
>>
>> Just occurred to me that I'm using fink and that git-am doesn't use
>> /usr/bin/sed but just sed. My suggestion is to be explicit on the
>> path in git-am.
>
> Then how would you work around a platform sed that is broken? You can't
> just install a new one in another directory if we use an absolute path.
> Which apparently is what people have to do on Solaris, see the
> SANE_TOOL_PATH setting for the Makefile.
>
> --
> Thomas Rast
> trast@{inf,student}.ethz.ch
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail