Dave Airlie wrote:
just apply the --unsafe as default patch I suppose, I'm not sure its
actually a useful feature,
I created an 'unsafe' mode by default patch and sent it upstream, as
well as noted it in the bug report. I'll go apply for privileges to
asciidoc so I can apply this, if no one
Todd Zullinger wrote:
I'm not sure how widely used asciidoc is around here. Both git and
tig use it to build their documentation and have been hit by bug
506953¹. I think this bug may hit many other users of asciidoc as
well, making our current packages a bit annoying to use for many
On Wed, Jul 15, 2009 at 6:01 AM, Todd Zullingert...@pobox.com wrote:
¹ https://bugzilla.redhat.com/506953
safekeep hit it. I was just starting to diagnose the problem.
Do we really need to carry patches around in multiple individual
projects for what is understood to be a problem in our
On Wed, Jul 15, 2009 at 11:12:19AM -0800, Jeff Spaleta wrote:
These are the packages which asciidoc's broken safe behavior.
potentially impacts on packaging building.
repoquery --whatrequires --archlist=src --repoid=rawhide-source asciidoc
git-cola-0:1.3.8-1.fc12.src
On Wed, 2009-07-15 at 10:01 -0400, Todd Zullinger wrote:
I'm not sure how widely used asciidoc is around here. Both git and
tig use it to build their documentation and have been hit by bug
506953¹. I think this bug may hit many other users of asciidoc as
well, making our current packages a
