Quick Start Mercurial: An introduction for the impatient. 

Thanks to the Author/Publisher.

1. Setting a username

The first thing you should do is set the username Mercurial will use for commits. It's best to configure a proper email address in ~/.hgrc ¹ (or on a Windows system in %USERPROFILE%\Mercurial.ini) by creating it and adding lines like the following:

[ui]
username = John Doe 

2. Working on an existing Mercurial project

If you have a URL to a browsable project repository (for example http://selenic.com/hg), you can grab a copy like so:

$ hg clone http://selenic.com/hg mercurial-repo
real URL is http://www.selenic.com/hg/
requesting all changes
adding changesets
adding manifests
adding file changes
added 9633 changesets with 19124 changes to 1271 files
updating to branch default
1084 files updated, 0 files merged, 0 files removed, 0 files unresolved

This will create a new directory called mercurial-repo, grab the complete project history, and check out the most recent changeset on the default branch.

The 'summary' command will summarize the state of the working directory. Command names may be abbreviated, so entering just 'hg sum' is enough:

$ hg sum
parent: 9632:16698d87ad20 tip
 util: use sys.argv[0] if $HG is unset and 'hg' is not in PATH
branch: default
commit: (clean)
update: (current)

Here commit: (clean) means that there no local changes, update: (current) means that 

the checked out files (in the working directory) are updated to the newest revision 

in the repository.  

3. Setting up a new Mercurial project

You'll want to start by creating a repository in the directory containing your project:

$ cd project/
$ hg init           # creates .hg

Mercurial will look for a file named .hgignore 
 in the root of your repository which contains a set of glob patterns 
and regular expressions to ignore in file paths. Here's an example .hgignore file: 

syntax: glob
*.orig
*.rej
*~
*.o
tests/*.err

syntax: regexp
.*\#.*\#$

Test your .hgignore file with 'status': 

$ hg status         # show all non-ignored files

This will list all files that are not ignored with a '?' flag (not tracked). 

Edit your '.hgignore' file until only files you want to track are listed by status. 

You'll want to track your .hgignore file too! But you'll probably not want to 
track files generated by your build process. Once you're satisfied, 
schedule your files to be added, then commit:  

$ hg add            # add those 'unknown' files
$ hg commit         # commit all changes into a new changeset, edit changelog entry
$ hg parents        # see the currently checked out revision (or changeset)

To get help on commands, simply run: 

$ hg help

4. Clone, commit, merge

 

$ hg clone project project-work    # clone repository
$ cd project-work
$ 
$ hg commit
$ cd ../project
$ 
$ hg commit
$ hg pull ../project-work   # pull changesets from project-work
$ hg merge                  # merge the new tip from project-work into our working directory
$ hg parents                # see the revisions that have been merged into the working directory
$ hg commit                 # commit the result of the merge

5. Exporting a patch

(make changes)
$ hg commit
$ hg export tip    # export the most recent commit

6. Network support

# clone from the primary Mercurial repo
$ hg clone http://selenic.com/hg/
$ cd hg

# pull new changesets from an existing other repo into the repository (.hg)
$ hg pull http://selenic.com/hg/

# export your current repo via HTTP with browsable interface on port 8000
$ hg serve -n "My repo"

# push changesets to a remote repo with SSH
$ hg push ssh://user@example.com/hg/

 

 

From Quality by Chance, To Quality by Design

1. What is testing?

An integral part of engineering
Set of activities performed to verify that desired level of quality exists in the product
Remember Murphy?
If anything can go wrong, it will...If there is a possibility of several things going
wrong, the one that will cause the most damage will be the one to go wrong
Courtsey:http://www.edwards.af.mil/history/docs_html/tidbits/murphy's_law.htm
l
2. What is software testing?





Integral part of software engineering
Set of activities performed to verify that desired level of quality exists in the software
An afterthought till recently
All quality movements (Unified process, agile methodologies, CMM, ISO etc.)
advocate serious software testing efforts
In practice, often done as a ritual, and often done, in isolation, without consideration
of overall software development effort
“Whatever you do, you are not done, until you have verified that you did what
you wanted to do”
Courtsey: Ivar Jacobson


Testing is not only an effort to verify that the software behaves as defined but also
to verify that it does not behave in an undesirable way even in the worst of
circumstances
Therefore, unlike other activities of software development, this requires traces of
pessimism and destructive approach
3. What is quality?


“In god, we trust”: a good quality policy ? No
“We do all right things, so the product should also be right”: : a good quality policy ?
No
Odds against error-free performance seem overwhelmingly high; there is only
one way of performing a task correctly or at best, very few; opportunity to stray
along a multitude of unintended or inappropriate pathways.... many ways to
bungle a simple operation
Courtsey: James Reason

There are as many definitions of quality as there are quality Gurus
From the practical business perspective, what satisfies, or better still delights, the
customer can be considered as a working definition
"Our job is to give the client not what he wants But what he never even dreamt
he wanted"
Courtsey: Sir Denys Lasdun

It is not an abstract notion but rather very specific & concrete, in the context of a
specific project, at the specific point in time
“Quality is not an act; it is a habit”
Courtsey: Aristotle
4. What is special about software?

Software development is inherently complex and creative activity, and involves
teamwork
“As such, I work from the premise that software development has been, is, and
will remain a fundamentally hard profession and no one thing will make a state
change in how we develop software”
Courtsey: Grady Booch
“Einstein argued that there must be simplified explanations of nature, because
God is not capricious or arbitrary. No such faith comforts the software engineer.
Much of the complexity that he must master is arbitrary complexity”
Courtsey: Fredreck Brooks
“Software is not limited by physics, like buildings are. It is limited by imagination,
by design, by organization. In short, it is limited by properties of people, not by
properties of the world..... We have not met the enemy, and he is us”
Courtsey: Martin Fowler
5. What goes wrong?



Software industry and, consequently software engineering, has been, and continues
to be, evolving at a drastic pace.
An average developer has an arduous task of building expertise on, and delivering
solutions using, brand new technologies that he has to work with.
This, combined with the pressure to churn out as much code as possible, leaves very
little room for adoption of the available process standards, methodologies and tools,
which in themselves are evolving.

Ubuntu

System Program Problem Detected on Ubuntu 12.10

 

 

 

 

type this in the terminal window "sudo rm /var/crash/*"

 

CS Research Paper

UML CS Research Paper Repository

Research Databases for Computer Science

Computer Science Students please visit the link above for the references of your research title.