From: Michael G Schwern <schwern@pobox.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, robbat2@gentoo.org,
bwalton@artsci.utoronto.ca, normalperson@yhbt.net
Subject: Re: Teach Makefile.PL to find .pm files on its own
Date: Wed, 25 Jul 2012 14:12:22 -0700 [thread overview]
Message-ID: <50106136.5000404@pobox.com> (raw)
In-Reply-To: <7vehnzbmyt.fsf@alter.siamese.dyndns.org>
On 2012.7.25 1:32 PM, Junio C Hamano wrote:
> Michael G Schwern <schwern@pobox.com> writes:
>
>> What's the lag time on it showing up in the repo, and which branch will it
>> appear in?
>
> There is nothing special in this topic, so it is likely to start on
> 'pu', and unlikely to come to 'master' before 1.7.12 ships sometime
> next month.
Ok.
>> Also I just realized I've been basing my work on master. Should I move to maint?
>
> I don't think so. It is not fixing any urgent breakage (iow, by
> being told about .pm explicitly, it knows about them just fine
> without being taught how to find them).
How about the git-svn SVN 1.7 fix in general? All of these patch sets I'm
sending build on one another, is that going to be a problem? It's going to
come in about six parts.
1) Makefile.PL .pm auto-find
2) Extract Git::SVN from git-svn
3) Extract the other modules from git-svn
4) Create and use accessors for paths and urls
5) Make the accessors canonicalize
6) Fix misc canonicalization issues
This is #1. #2 was submitted last night. #3 will be coming today. #4 should
probably wait until #3 is at least in pu and I stop moving around large chunks
of code.
#1 to #4 are all refactorings with no functional changes. #5 and #6 will be
tricky to provide as small commits while keeping all tests passing in SVN 1.6.
We'll see when I get there after doing the rebasing necessary to separate #4,
#5 and #6.
--
10. Not allowed to purchase anyone's soul on government time.
-- 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-25 21:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 3:21 Teach Makefile.PL to find .pm files on its own Michael G. Schwern
2012-07-25 3:21 ` [PATCH 1/3] Quiet warning if Makefile.PL is run with -w and no --localedir Michael G. Schwern
2012-07-25 3:21 ` [PATCH 2/3] Don't lose Error.pm if $@ gets clobbered Michael G. Schwern
2012-07-25 3:21 ` [PATCH 3/3] The Makefile.PL will now find .pm files itself Michael G. Schwern
2012-07-25 21:11 ` Jonathan Nieder
2012-07-25 21:31 ` Jonathan Nieder
2012-07-25 21:49 ` Michael G Schwern
2012-07-25 21:56 ` Jonathan Nieder
2012-07-25 16:56 ` Teach Makefile.PL to find .pm files on its own Junio C Hamano
2012-07-25 20:26 ` Michael G Schwern
2012-07-25 20:32 ` Junio C Hamano
2012-07-25 21:12 ` Michael G Schwern [this message]
2012-07-25 22:19 ` Junio C Hamano
2012-07-25 22:56 ` Michael G Schwern
2012-07-25 23:29 ` Junio C Hamano
2012-07-25 23:37 ` Eric Wong
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=50106136.5000404@pobox.com \
--to=schwern@pobox.com \
--cc=bwalton@artsci.utoronto.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).