stymied by default update

[Matt Mackall]

On Tue, 2014-12-30 at 17:44 -0500, John Turner wrote:
> On Tue, 30 Dec 2014 17:37:11 -0500, John Turner <jjturner at energi.com>  
> wrote:
> 
> > Greetings,
> >
> > Still learning the ropes here -
> > 1) the head commit to my new repo was an add of 655 files

We call this the root. Heads are on the other end of history.

> > 2) the next changeset was an add of 5 files
> > 3) the next changeset added 2 ignore patterns to .hgignore which wouldn't
> > affect the existing files in the repo - only unadded files currently
> > sitting in the working directory

Ignore patterns sole reason for existence is to decide which UNKNOWN
files are not interesting. Known, tracked files are interesting by
definition, so we don't ignore them. Every SCM I'm aware of works this
way.

> As a reference, here is the log (the "-1:000000000000" seems to be telling  
> me something..):
> E:\rmat_app>hg log
> changeset:   3:30cf64386e8d
> tag:         tip
> user:        jt
> date:        Tue Dec 30 17:26:30 2014 -0500
> summary:     reverting to just ignore of .rpt files
> 
> changeset:   2:cce500291c6a
> user:        jt
> date:        Tue Dec 30 14:58:49 2014 -0500
> summary:     ignoring anything in reports\base folder
> 
> changeset:   1:001d10e9ced9
> parent:      -1:000000000000
> user:        jt
> date:        Tue Dec 30 13:45:37 2014 -0500
> summary:     adding 5 files at repo root

When you did this commit, you had nothing (aka -1 aka 000000 aka null)
checked out. Perhaps you did:

$ hg init repo2 # empty repo with null checked out
$ cd b
$ hg pull path-to-repo1 # push/pull does not affect check-out

-- 
Mathematics is the supreme nostalgia of our time.