public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Junio C Hamano <junkio@cox•net>
To: "Marco Costalba" <mcostalba@gmail•com>
Cc: git@vger•kernel.org, junkio@cox•net
Subject: Re: [PATCH] Add a Documentation/git-tools.txt
Date: Sun, 19 Feb 2006 02:59:12 -0800	[thread overview]
Message-ID: <7vlkw7iphb.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <e5bfff550602190200j1ef3858as6a1564064dc81fef@mail.gmail.com> (Marco Costalba's message of "Sun, 19 Feb 2006 11:00:31 +0100")

"Marco Costalba" <mcostalba@gmail•com> writes:

> 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.

next prev parent reply	other threads:[~2006-02-19 10:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 10:00 [PATCH] Add a Documentation/git-tools.txt Marco Costalba
2006-02-19 10:59 ` Junio C Hamano [this message]
2006-02-19 12:04   ` Marco Costalba
2006-02-19 12:25 ` Alan Chandler
2006-02-19 12:39   ` Marco Costalba
2006-02-20  2:01 ` Jonas Fonseca
2006-02-20  6:21   ` Marco Costalba
2006-02-20 10:31 ` Catalin Marinas
2006-02-26  8:22   ` Marco Costalba
2006-02-26 22:51     ` Junio C Hamano
2006-02-27  6:44       ` Marco Costalba
2006-02-27  8:39       ` Alexandre Julliard
2006-03-04  6:42         ` Marco Costalba

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vlkw7iphb.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox$(echo .)net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=mcostalba@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox