From: Michael G Schwern <schwern@pobox.com>
To: kusmabite@gmail.com
Cc: git@vger.kernel.org, gitster@pobox.com, robbat2@gentoo.org,
bwalton@artsci.utoronto.ca, normalperson@yhbt.net,
jrnieder@gmail.com
Subject: Re: Extract remaining classes from git-svn
Date: Fri, 27 Jul 2012 12:00:06 -0700 [thread overview]
Message-ID: <5012E536.5080507@pobox.com> (raw)
In-Reply-To: <CABPQNSYjvW9GZs18j+m4mUT6jiJ5VTUdnyi-L5Q8tHeqE7R+tg@mail.gmail.com>
On 2012.7.27 4:29 AM, Erik Faye-Lund wrote:
> On Fri, Jul 27, 2012 at 2:27 AM, Michael G Schwern <schwern@pobox.com> wrote:
>> On 2012.7.26 5:25 PM, Michael G. Schwern wrote:
>>> This series of patches extracts the remaining classes from git-svn. They're
>>> all simple extractions and functionally have no change.
>>
>> PS This is on top of the previous Git::SVN extraction patch series.
>>
>
> Nice :-)
>
> Do you have somewhere I can pull this from? I have a git-svn topic
> that I suspect will be much easier to maintain on top of these
> patches.
Why yes I do!
https://github.com/schwern/git
The git-svn branches should be fairly self explanatory and they stack on top
of each other. I'll probably be doing a lot of rebasing still, but there
should be little content change up to git-svn/canonicalize-accessors. Up to
there passes tests with SVN 1.6.
Things get a little fuzzy after that.
--
24. Must not tell any officer that I am smarter than they are, especially
if it's true.
-- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
http://skippyslist.com/list/
next prev parent reply other threads:[~2012-07-27 19:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 0:25 Extract remaining classes from git-svn Michael G. Schwern
2012-07-27 0:26 ` [PATCH 1/8] Prepare Git::SVN::Log for extraction " Michael G. Schwern
2012-07-27 0:26 ` [PATCH 2/8] Extract Git::SVN::Log " Michael G. Schwern
2012-07-27 0:26 ` [PATCH 3/8] Prepare Git::SVN::Migration for extraction " Michael G. Schwern
2012-07-27 0:26 ` [PATCH 4/8] Extract Git::SVN::Migration " Michael G. Schwern
2012-07-27 0:26 ` [PATCH 5/8] Load all the modules in one place and before running code Michael G. Schwern
2012-07-27 0:26 ` [PATCH 6/8] Move Git::IndexInfo into its own file Michael G. Schwern
2012-07-27 0:26 ` [PATCH 7/8] Extract Git::SVN::GlobSpec from git-svn Michael G. Schwern
2012-07-27 0:26 ` [PATCH 8/8] Fix indents to match style Michael G. Schwern
2012-07-27 0:27 ` Extract remaining classes from git-svn Michael G Schwern
2012-07-27 11:29 ` Erik Faye-Lund
2012-07-27 19:00 ` Michael G Schwern [this message]
2012-07-28 0:40 ` Eric Wong
2012-07-28 4:05 ` Junio C Hamano
2012-07-28 4:12 ` Eric Wong
2012-07-28 4:25 ` 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=5012E536.5080507@pobox.com \
--to=schwern@pobox.com \
--cc=bwalton@artsci.utoronto.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=kusmabite@gmail.com \
--cc=normalperson@yhbt.net \
--cc=robbat2@gentoo.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.