[SCM] Debian Packaging Handbook: wiki source branch, master, updated. 6dffb77615497e638432f2ffa16a77ecf3969334

[Luca Brivio]

The branch, master has been updated
       via  6dffb77615497e638432f2ffa16a77ecf3969334 (commit)
      from  3f495a2e197b0a02733b15fd708bc2ed6c38ba88 (commit)


- Shortlog ------------------------------------------------------------
6dffb77 web commit by LucaBrivio: DocBook doesn't allow emphasis within literal elements

Summary of changes:
 Intro.adoc |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
-----------------------------------------------------------------------
Details of changes:

commit 6dffb77615497e638432f2ffa16a77ecf3969334
Author: Luca Brivio <lb-guest at alioth.debian.org>
Date:   Tue Jan 22 10:22:15 2008 +0000

    web commit by LucaBrivio: DocBook doesn't allow emphasis within literal elements

diff --git a/Intro.adoc b/Intro.adoc
index ae14915..6518e53 100644
--- a/Intro.adoc
+++ b/Intro.adoc
@@ -37,8 +37,8 @@ There are quite a few things you need to take into consideration when choosing s
 What to do before packaging
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- Ensure that the package is not in Debian already. An `apt-cache search 'pkgname'`, followed by a search on Google to find out whether the package already has been packaged as a ""deb"" should be sufficient. Don't duplicate work already done, you'll feel badly knowing that you've spent a week on packaging something someone has already been packaged months ago!
-- File an "Intent to Package" (ITP) bug to the Debian project, and CC the bug report to the debian-developers mailing list (reportbug does this automatically). The people on debian-devel might have some comments to make on your proposed ITP. If there isn't any opposition for a period of time, (say a week), you can assume that nobody opposes your intention of packaging the software.
+- Ensure that the package is not in Debian already. An `apt-cache search <pkgname>`, followed by a search on Google to find out whether the package already has been packaged as a ``deb'' should be sufficient. Don't duplicate work already done, you'll feel badly knowing that you've spent a week on packaging something someone has already been packaged months ago!
+- File an ``Intent to Package'' (ITP) bug to the Debian project, and CC the bug report to the debian-developers mailing list (reportbug does this automatically). The people on debian-devel might have some comments to make on your proposed ITP. If there isn't any opposition for a period of time, (say a week), you can assume that nobody opposes your intention of packaging the software.
 
 Sending an ITP
 ~~~~~~~~~~~~~~

-- 
Debian Packaging Handbook: wiki source