From: Seth Falcon <sethfalcon@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFH] git-svn documentation
Date: Wed, 18 Oct 2006 10:22:46 -0700 [thread overview]
Message-ID: <m2mz7tr121.fsf@ziti.local> (raw)
In-Reply-To: <20061016183101.GL27128@hand.yhbt.net> (Eric Wong's message of "Mon, 16 Oct 2006 11:31:02 -0700")
Eric Wong <normalperson@yhbt.net> writes:
> Anybody willing to supply patches for better documentation? I'll be
> quite busy with other projects the next two weeks, asciidoc is quite
> slow for me; but I'd like to have better docs for git-svn in 1.4.3.
I'm starting to use git-svn more and would be willing to attempt to
contribute some additional docs. What I have in mind is a howto use
git-svn sort of document (unless that isn't seen as useful)
... unfortunately, as I use git-svn more I'm encountering some
questions which will need resolution before I can have much confidence
in my howto :-\
Will post some howto and questions separately.
+ seth
prev parent reply other threads:[~2006-10-18 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 22:09 git-svn and u-boot broken Joakim Tjernlund
2006-10-16 3:47 ` Eric Wong
2006-10-16 10:06 ` Joakim Tjernlund
2006-10-16 18:31 ` [RFH] git-svn documentation [was Re: git-svn and u-boot broken] Eric Wong
2006-10-16 21:44 ` Joakim Tjernlund
2006-10-18 17:22 ` Seth Falcon [this message]
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=m2mz7tr121.fsf@ziti.local \
--to=sethfalcon@gmail.com \
--cc=git@vger.kernel.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.