Re: [PATCH] Add a Documentation/git-tools.txt
- From
Junio C Hamano <junkio@cox.net>
- Date
- Feb 19, 2006, 10:59 UTC
- Message-ID
- <7vlkw7iphb.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <e5bfff550602190200j1ef3858as6a1564064dc81fef@mail.gmail.com>
"Marco Costalba" <mcostalba@gmail.com> writes:
Show 10 quoted lines
> A brief survey of useful git tools, including third-party > and external projects. > > Signed-off-by: Marco Costalba <mcostalba@gmail.com> > --- > > Please consider this more of a RFC then a finished patch. > > Where possible, for each tool, the author's description is used as a summary. > I found http://git.or.cz/ a good source.
Thanks for starting this.
Briefly mentioning tool's strength and weakness without being too subjective would be very helpful to potential users. We would encourage competition without making other tools sound inferiour on subjective terms. So "this is similar to foobar tool, but runs much faster, but has these limitations" would be a good style, but "this draws much nicer picture than barboz" without substantiating why it is nicer may be suboptimal. Also I am a bit afraid that the summary can become stale unless maintained actively. Hopefully the respective authors of tools can keep us updated.
I am of two minds about mentioning things available from the git repository, but I think it makes the survey more complete and more useful in general to include them in the list. The private draft I sent out to you earlier forgot to include the foreign SCM interfaces.