[BUG] inconsistent output of hg parents
Daniel Santa Cruz
byteshack at gmail.com
Mon Apr 10 21:38:44 UTC 2006
Sorry all, seems that I've answered my own question. This was a
misunderstanding/misuse of what hg parents would do. It returns the
parent of the working directory! Duh! hg parents REV does give the
correct output. Seems that the bug tracking database was after all
smarter than me.
Daniel.
On 4/10/06, Daniel Santa Cruz <byteshack at gmail.com> wrote:
> hg parents on a working directory that contains the merged files but
> has not been commited yet:
>
> $ hg parents
> changeset: 3285:7ec1414f3847
> user: "***"
> date: Fri Apr 07 09:55:48 2006 -0500
> summary: Re #1291
>
> changeset: 3295:70ac72c896bd
> tag: tip
> parent: 3294:e235590a52e4
> parent: 3283:dfe6e2263fcf
> user: "***"
> date: Fri Apr 07 08:45:23 2006 -0500
> summary: merging with trunk
>
> While the output of hg parents after one has "hg update -C"'ed to a
> revision that has multiple parents is:
>
> $ hg parents
> changeset: 3289:70ac72c896bd
> tag: tip
> parent: 3288:e235590a52e4
> parent: 3279:dfe6e2263fcf
> user: "***"
> date: Fri Apr 07 08:45:23 2006 -0500
> summary: merging with trunk
>
>
> Can we have a consistent output for these 2 scenarios?
>
> Daniel.
>
>
> NOTE: I just tried to add that same text on the bug db, but it had a
> cow. Here is the exception that it threw:
>
> A problem occurred while running a Python script. Here is the sequence
> of function calls leading up to the error, with the most recent
> (innermost) call first. The exception attributes are:
> __doc__ = 'I/O operation failed.'
> __getitem__ = <bound method IOError.__getitem__ of
> <exceptions.IOError instance>>
> __init__ = <bound method IOError.__init__ of <exceptions.IOError
> instance>>
> __module__ = 'exceptions'
> __str__ = <bound method IOError.__str__ of <exceptions.IOError instance>>
> args = (13, 'Permission denied')
> errno = 13
> filename =
> '/home/oxymoron/selenic/roundup/trackers/mercurial/db/files/msg/1/msg1002.tmp'
> strerror = 'Permission denied'
>
More information about the Mercurial
mailing list