threads / discuss / 23978

Documentation on writing portable code for Git

Subject: Documentation on writing portable code for Git

## tl;dr

One message between Jun 2, 2010 and Jun 2, 2010.

replies: 0people: 1as markdown or json

Ævar Arnfjörð Bjarmason· Jun 2, 2010, 09:42 UTC · lore
On Wed, Jun 2, 2010 at 06:41, Johannes Sixt <j.sixt@viscovery.net> wrote:
Show 7 quoted lines
> Am 6/2/2010 2:13, schrieb Brandon Casey:
>>  test_expect_success 'setup' '
>> -     unset GIT_PAGER GIT_PAGER_IN_USE &&
>> +     unset GIT_PAGER GIT_PAGER_IN_USE
>
> Maybe we should terminate the line with ';' to document that it is a
> deliberate choice that there is no '&&'?

(Split from the "ignore return status of shell's unset builtin" thread)

It would be nice if there was documentation describing how to write portable code for various parts of Git. Basically a bullet-point aggregate of the subjects of various patches we keep getting from users of IRIX, Solaris, HP-UX etc. E.g:

    * Use FOO=bar and then export FOO, not export FOO=bar
    * Don't check the return value of unset, Solaris ...
I could contribute some of these for Perl.

← back to recent threads