Andreas Ericsson [off-list ref] writes:
When gc was a shell-script, it was fairly easy to find out the command-
sequence...
Maybe referring more advanced/curious users to contrib/examples/
directory is a good idea, but not necessarily from manpages of
the commands that have been rewritten in C.
I think contrib/examples/ needs a README file that effectively
say "these are the last versions of shell script implementation
of the commands before they were rewritten in C. New features
may have been added to the built-in ones but these example
scripts are not kept up to date. They are here to serve as
examples to show you how you would pipeline the plumbing level
commands."
Junio C Hamano wrote:
Andreas Ericsson [off-list ref] writes:
quoted
When gc was a shell-script, it was fairly easy to find out the command-
sequence...
Maybe referring more advanced/curious users to contrib/examples/
directory is a good idea, but not necessarily from manpages of
the commands that have been rewritten in C.
I think contrib/examples/ needs a README file that effectively
say "these are the last versions of shell script implementation
of the commands before they were rewritten in C. New features
may have been added to the built-in ones but these example
scripts are not kept up to date. They are here to serve as
examples to show you how you would pipeline the plumbing level
commands."
Sensible, and also avoids the possible bitrot problem with the
man-page should there be additional actions added to standard
git-gc operations.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231