On Sat, Apr 17, 2021 at 10:43:54AM +0200, Ævar Arnfjörð Bjarmason wrote: > Remove a suggestion to write new commands in Perl or Shell to > experiment. This advice was added in 6d0618a820a (Add > Documentation/CodingGuidelines, 2007-11-08). > > Since then the consensus changed to having no new such commands unless > necessary, and existing ones have been actively migrated to C. > > Signed-off-by: ??var Arnfj??r?? Bjarmason <avarab@xxxxxxxxx> The patch looks good - but the Umlauts are garbled: ISO-2022-JP is used ? > --- > Documentation/CodingGuidelines | 5 ----- > 1 file changed, 5 deletions(-) > > diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines > index 45465bc0c98..b9cd55db6a8 100644 > --- a/Documentation/CodingGuidelines > +++ b/Documentation/CodingGuidelines > @@ -416,11 +416,6 @@ For C programs: > that are made available to it by including one of the header files > it must include by the previous rule. > > - - If you are planning a new command, consider writing it in shell > - or perl first, so that changes in semantics can be easily > - changed and discussed. Many Git commands started out like > - that, and a few are still scripts. > - > - Avoid introducing a new dependency into Git. This means you > usually should stay away from scripting languages not already > used in the Git core command set (unless your command is clearly > -- > 2.31.1.687.g1d87aeed692 >
