From: Martin Langhoff <martin.langhoff@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 0.99.5
Date: Thu, 25 Aug 2005 15:30:53 +1200 [thread overview]
Message-ID: <46a038f9050824203027fbca0@mail.gmail.com> (raw)
In-Reply-To: <7vr7ci4u7q.fsf@assigned-by-dhcp.cox.net>
On 8/25/05, Junio C Hamano <junkio@cox.net> wrote:
> Have fun.
Yay!
> What to expect after 0.99.5
> ===========================
> Documentation
> -------------
Perhaps link the 'howto' docs from the git formal docs, so they are
visible via http://www.kernel.org/pub/software/scm/git/docs/
> * Accept patches from people who actually have done CVS
> migration and update the cvs-migration documentation.
> Link the documentation from the main git.txt page.
Yup, run trial conversions for about half a dozen cvs repos, and
currently tracking external cvs projects with git too. Will update
docs as I find time.
> * Update tutorial to cover shared repository style a bit more,
> maybe with a toy project that involves two or three
> repositories.
I recently wrote one such 'shared repo' tutorial for internal
consumption at work. Should clean it up, and add to the howto dir. The
incentive here would be to see the howtos on the web - and then I can
point people at it directly.
> Technical (milder)
> ------------------
Personally, I want to complete the Arch import. I'm interested in
feedback on the current code -- anyone has an interest in migration
from Arch or similar patch-centric SCM?
cheers,
martin
next prev parent reply other threads:[~2005-08-25 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 2:38 [ANNOUNCE] GIT 0.99.5 Junio C Hamano
2005-08-25 3:30 ` Martin Langhoff [this message]
2005-08-25 19:05 ` Darrin Thompson
2005-08-26 15:12 ` Eric W. Biederman
2005-08-26 16:24 ` Junio C Hamano
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=46a038f9050824203027fbca0@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).