From: Michael G Schwern <schwern@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com,
"Robin H. Johnson" <robbat2@gentoo.org>,
Eric Wong <normalperson@yhbt.net>,
Ben Walton <bwalton@artsci.utoronto.ca>
Subject: Re: git-svn SVN 1.7 fix, take 2
Date: Tue, 24 Jul 2012 15:50:39 -0700 [thread overview]
Message-ID: <500F26BF.7090501@pobox.com> (raw)
In-Reply-To: <20120724220207.GA15969@burratino>
On 2012.7.24 3:02 PM, Jonathan Nieder wrote:
>> The Git::SVN extraction is more complicated than the rest, so I'll probably do
>> that separately and bust it up into a few commits.
>
> All of these changes are supposed to have zero functional effect,
> right?
Right. They're just class extraction refactoring. I don't even need to make
new classes, they already exist. It's just moving them into their own file.
> Could you send the first five patches that *are* supposed to have a
> functional effect? I know that they will not apply cleanly to git-svn
> from git "master" or on top of each other; that's fine with me. If
> the approach looks right, interested people (read: probably Ben or I :))
> can make the corresponding change in the code layout from "master".
> Afterwards, we can look into all that refactoring to make later
> changes easier.
>
> What do you think?
I think that would be a lot of extra work for me, create a big mess and be
harder to understand. :-/
Since I'm creating new files to store the classes, the functional changes
cannot be applied without the class extractions, so I'd have to rewrite them.
And they will be harder to review since the main git-svn code and the class
code is mixed up in one file. And they won't have unit tests, since git-svn
cannot be loaded without it running.
The Git::SVN extraction isn't really complicated, it just requires a handful
more work than the other classes. Just a few method extractions. The rest
are essentially cut, paste & fix lexicals.
I'm not sure what you're going for, but you can glance through the existing
changes here
https://github.com/schwern/git/commits/git-svn/fix-canonical
or you can do grab it as a remote and...
git log -p schwern/git-svn/extract-classes..schwern/git-svn/fix-canonical
That should give you the information you need... if I understand what you
need. I feel like I don't and we're talking past each other.
--
Ahh email, my old friend. Do you know that revenge is a dish that is best
served cold? And it is very cold on the Internet!
next prev parent reply other threads:[~2012-07-24 22:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 21:46 git-svn SVN 1.7 fix, take 2 Michael G Schwern
2012-07-24 21:51 ` Junio C Hamano
2012-07-24 23:06 ` Michael G Schwern
2012-07-24 23:12 ` Jonathan Nieder
2012-07-24 22:02 ` Jonathan Nieder
2012-07-24 22:50 ` Michael G Schwern [this message]
2012-07-24 23:03 ` Jonathan Nieder
2012-07-24 23:31 ` Jonathan Nieder
2012-07-24 23:45 ` Junio C Hamano
2012-07-25 1:00 ` Michael G Schwern
2012-07-25 4:53 ` Jonathan Nieder
2012-07-25 5:36 ` Michael G Schwern
2012-07-25 7:14 ` Junio C Hamano
2012-07-25 9:53 ` Michael G Schwern
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=500F26BF.7090501@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=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.