diff --git a/EliveUsersGuide.md b/EliveUsersGuide.md
index cb6e74e..05218df 100644
--- a/EliveUsersGuide.md
+++ b/EliveUsersGuide.md
@@ -72,6 +72,32 @@ There are a few documentations that will help solve any problems we encounter du
 
 # Debian Package Building 
 
+
+
+If using code management system (VCS) to maintain code, this merge and upstream patches a lot easier.
+
+Requirement:
+git-buildpackage: a suite to help with Debian packages in Git repositories.
+Svn-buildpackage: helper programs to maintain Debian packages with Subversion.
+cvs-buildpackage: a set of Debian package scripts for CVS source trees.
+This makes merging and cherry-picking upstream patches easier.
+Git-build-packages is becoming poplar for developers to manage Debian.
+
+Structure:
+main: for Debian package source tree.
+Upstream: for upstream source tree.
+Pristine-tar: for upstream tarball generated by the –pristine-tar option.
+
+Formatting: 
+Theses commands automate packing activites
+git-import-dsc(1): import a previous Debian package to a Git repository.
+git-import-orig(1): import a new upstream tar to a Git repository.
+git-dch(1): generate: the Debian changelog from Git commit messages.
+git-buildpackage(1): build Debian packages from a Git repository.
+git-pbuilder(1): build Debian packages from a Git repository using pbuilder/cowbuilder.
+
+#This link below will show you what is new in the patches and what will be in the upcoming patches. http://alioth.debian.org/
+
 ## Workflow
 
     1. Get a copy of the upstream software, usually in a compressed tar format.
@@ -88,7 +114,6 @@ There are a few documentations that will help solve any problems we encounter du
 
 ## Import Upstream
 
-
     1. First, create the first version of a package, outside of Git. Once it done, you can import the package using the import-dsc command.
 
 ~~~shell