From: "J. Bruce Fields" <bfields@fieldses.org>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Remove 'submodules' from the TODO section of the User Manual.
Date: Tue, 25 Sep 2007 16:13:06 -0400 [thread overview]
Message-ID: <20070925201306.GW30845@fieldses.org> (raw)
In-Reply-To: <20070925200252.GV30845@fieldses.org>
On Tue, Sep 25, 2007 at 04:02:52PM -0400, bfields wrote:
> I think we should try to keep the git documentation mostly confined to
> tools that are distributed with git itself. So it might be worth a few
> words just to mention the existance of tailor and how it compares to
> other tools, but I'd leave it at that.
So in fact it might be that what's needed isn't any new documentation on
the available tools with their features and limitations.
I know that when I recently had to deal with a svn tree the hardest part
was figuring out where to start (git-svn? git-svnimport?). I seem to
recall threads here suggesting this is a general problem.
One exception--the "series of tarballs" thing--I think it's cool that
you can just unpack a bunch of tarballs and string them together into a
git history. It gives a good sense of how git works, and I don't think
it's documented explicitly anywhere. I think that might be kinda fun to
write up. But I haven't tried.
--b.
next prev parent reply other threads:[~2007-09-25 20:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 19:11 [PATCH] Remove 'submodules' from the TODO section of the User Manual Miklos Vajna
2007-09-25 19:23 ` J. Bruce Fields
2007-09-25 19:47 ` Miklos Vajna
2007-09-25 19:49 ` J. Bruce Fields
2007-09-25 19:57 ` Miklos Vajna
2007-09-25 20:02 ` J. Bruce Fields
2007-09-25 20:13 ` J. Bruce Fields [this message]
2007-09-25 20:16 ` J. Bruce Fields
2007-09-25 22:37 ` [PATCH] User Manual: document import-tars.perl Miklos Vajna
2007-09-26 18:14 ` J. Bruce Fields
2007-09-26 18:22 ` Miklos Vajna
2007-09-26 20:37 ` J. Bruce Fields
2007-09-26 19:58 ` Johannes Schindelin
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=20070925201306.GW30845@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vmiklos@frugalware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.