Front page | perl.perl5.porters |
Postings from June 2012
On Fri, 15 Jun 2012 13:10:57 -0700, "Father Chrysostomos via RT"
<perlbug-comment@perl.org> wrote:
> On Sun Jul 10 18:43:42 2011, sprout wrote:
> > I can take a reference to a subroutine with a string (which
> > autovivifies a stub):
> >
> > \&{"foo"}
> >
> > I can assign that to the *{""} glob and then take a reference to that:
> >
> > *{""} = \&{"foo"}
> > \&{""}
> >
> > But if I try to take a reference to &{""} to begin with,
> > autovivification fails and causes an error:
> >
> > $ perl -le '*foo = \&{""}'
> > Unable to create sub named "" at -e line 1.
>
> I fixed this in commit 186a5ba82, but I don’t know how to stop git
> rebase -i from eating parts of the commit message, and I always forget
> about this:
>
> ...While bug
> #107370 still persists, bug #94476 (\&{""} not autovivifying) has
> been fixed, as it was a side effect of sv_2cv triggering bug #107370.
lines starting with a # are considered comment and not kept iirc
> becoming this:
>
> ...While bug
> been fixed, as it was a side effect of sv_2cv triggering bug #107370.
>
> So the commit message is gibberish. And I only realised after pushing it.
>
> Is there any way to set git preferences so it doesn’t do that (and
> doesn’t attach git status output to the file containing the commit message)?
>
--
H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/
using perl5.00307 .. 5.14 porting perl5 on HP-UX, AIX, and openSUSE
http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/
http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
Thread Previous
|
Thread Next