From: Junio C Hamano <gitster@pobox.com>
To: Michael G Schwern <schwern@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 15:19:13 -0700 [thread overview]
Message-ID: <7vsjcfa3ha.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <50106136.5000404@pobox.com> (Michael G. Schwern's message of "Wed, 25 Jul 2012 14:12:22 -0700")
Michael G Schwern <schwern@pobox.com> writes:
>>> 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.
Judging from the rate of the discussion this is progressing, I was
imagining that this series would be ready by 1.7.13 at the earliest,
possibly back-merged to 1.7.12.X maintenance series, and 1.7.11.X
maintenance series is no longer relevant by then.
But I certainly do not mind seeing the series based on earlier
maintenance releases, e.g. maint-1.7.9. There however are tons of
other git-svn.perl and perl/ updates since then, so basing the
series on the current maint branch to abandon 1.7.10.X and earlier
but still leaving the door open to downmerge to 1.7.11.X may be a
good trade-off.
next prev parent reply other threads:[~2012-07-25 22:19 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
2012-07-25 22:19 ` Junio C Hamano [this message]
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=7vsjcfa3ha.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bwalton@artsci.utoronto.ca \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=robbat2@gentoo.org \
--cc=schwern@pobox.com \
/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).