From: "J. Bruce Fields" <bfields@fieldses.org>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] User Manual: document import-tars.perl
Date: Wed, 26 Sep 2007 16:37:36 -0400 [thread overview]
Message-ID: <20070926203736.GC26099@fieldses.org> (raw)
In-Reply-To: <20070926182204.GB14959@genesis.frugalware.org>
On Wed, Sep 26, 2007 at 08:22:04PM +0200, Miklos Vajna wrote:
> On Wed, Sep 26, 2007 at 02:14:51PM -0400, "J. Bruce Fields" <bfields@fieldses.org> wrote:
> > Neat-o, I'd missed (or forgotten about) import-tars.perl.
> >
> > But I'd prefer to keep this first explanation of how to initialize and
> > commit to a new project pretty streamlined, and I don't think this is
> > really necessary here. So let's save this up until we have enough
> > material for a separate chapter or section on interacting with other
> > scm's.
>
> okay, now it's saved by gmane :)
Also in my git tree--I took yours and Johannes' suggestions, put them in
a blender, and added a brief skeleton of a new chapter at:
git://linux-nfs.org/~bfields/git.git docwork-foreign-scms
--b.
next prev parent reply other threads:[~2007-09-26 20:38 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
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 [this message]
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=20070926203736.GC26099@fieldses.org \
--to=bfields@fieldses.org \
--cc=Johannes.Schindelin@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).