develooper Front page | perl.perl5.porters | Postings from June 2008

Re: [PATCH 04/10] Ignore DynaLoader.xs in .gitignore for DynaLoader.

Thread Previous | Thread Next
Sam Vilain
June 25, 2008 03:02
Re: [PATCH 04/10] Ignore DynaLoader.xs in .gitignore for DynaLoader.
Message ID:
Florian Ragwitz wrote:
> On Wed, Jun 25, 2008 at 08:44:31AM +0200, Rafael Garcia-Suarez wrote:
>> 2008/6/25 Florian Ragwitz <>:
>>> ---
>>>  ext/DynaLoader/.gitignore |    1 +
>>>  1 files changed, 1 insertions(+), 0 deletions(-)
>> Perl has not switched to git yet. This file does not exist.
> I just saw that those .gitignore files are only available in Sams git
> mirror right now. I should have sent them to him directly.

Yes, that was a mistake.  It wasn't my intention to start applying
patches not endorsed by Pumpkings.  And my irregular update script
wasn't verbose enough about the failure.

That being said I think they are valuable to people tracking the
repository.  so, here's what I'll do;

 'p4/perl' will have the inadvertant commit removed from it and track
   perforce verbatim.

 'blead' will get merged from blead every time I update it, and I'll
   review and accept changes to files under Porting/ and any git
   interoperability-related patches I receive and can be convinced are

My intention with accepting these changes is that patches to Porting/
would give instructions about how all of the maintenance operations that
worked under Perforce will work under git.  In particular, there should
be a script which will use the output of 'git rev-list --cherry-pick',
as well as correlate information from the log messages, to say what
patches still need to be considered for application to the maintenance

I'm hoping that this will stop there every being a fork while not
discouraging people who are willing to help the transition help out.

If anyone has any objections, please raise them - I can of course just
put these under a different branch or something like that.


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About