qnew ignores -u unless username is configured

[Kyle Altendorf-2]

It appears that the qnew command ignores the -u option unless I have
set a username in one of my config files.  I tried the following with
and without a configured username:

mkdir test.qnewUsername
cd test.qnewUsername
hg init
hg qnew red -u blue

Without a configured username the last line responded with:

> abort: Please specify a username.

With a configured username (that was not 'blue') it worked as I would
have expected creating a blank patch containing:

> From: blue
>
>

I am on Windows XP with the latest TortoiseHg release candidate
installed.  hg version reports:

> Mercurial Distributed SCM (version 1.3.1+295-1de5ebfa5585)

Certainly I will just specify a username for now but am I doing
something wrong or is this a bug?

Thanks,
-kyle
_______________________________________________
Mercurial mailing list
Mercurial@...
http://selenic.com/mailman/listinfo/mercurial

[Martin Geisler-4]

Kyle Altendorf <kyle.altendorf@...> writes:

> It appears that the qnew command ignores the -u option unless I have
> set a username in one of my config files. [...]
>
> Certainly I will just specify a username for now but am I doing
> something wrong or is this a bug?

It is a bug, thanks a lot for the detailed report. I've fixed it in
f16ec85f125c, so please try again with a release candidate that says

  Mercurial Distributed SCM (version 1.3.1+362-f16ec85f125c)

or higher, that is 1.3.1+X-blabla with a higher X.

--
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.


_______________________________________________
Mercurial mailing list
Mercurial@...
http://selenic.com/mailman/listinfo/mercurial

[Kyle Altendorf-2]

On Sat, Nov 7, 2009 at 3:04 AM, Martin Geisler <mg@...> wrote:

> Kyle Altendorf <kyle.altendorf@...> writes:
>
>> It appears that the qnew command ignores the -u option unless I have
>> set a username in one of my config files. [...]
>>
>> Certainly I will just specify a username for now but am I doing
>> something wrong or is this a bug?
>
> It is a bug, thanks a lot for the detailed report. I've fixed it in
> f16ec85f125c, so please try again with a release candidate that says
>
>  Mercurial Distributed SCM (version 1.3.1+362-f16ec85f125c)
>
> or higher, that is 1.3.1+X-blabla with a higher X.
>

Sorry for the delayed response.  I just setup Mercurial from source
(much easier than expected...  :]  ) and it looks good (but you
already knew that).  Thanks for the extremely quick response.  I'm
impressed as usual.

Thanks,
-kyle
_______________________________________________
Mercurial mailing list
Mercurial@...
http://selenic.com/mailman/listinfo/mercurial

[Martin Geisler-4]

Kyle Altendorf <kyle.altendorf@...> writes:

> On Sat, Nov 7, 2009 at 3:04 AM, Martin Geisler <mg@...> wrote:
>> Kyle Altendorf <kyle.altendorf@...> writes:
>>
>>> It appears that the qnew command ignores the -u option unless I have
>>> set a username in one of my config files. [...]
>>>
>>> Certainly I will just specify a username for now but am I doing
>>> something wrong or is this a bug?
>>
>> It is a bug, thanks a lot for the detailed report. I've fixed it in
>> f16ec85f125c, so please try again with a release candidate that says
>>
>>  Mercurial Distributed SCM (version 1.3.1+362-f16ec85f125c)
>>
>> or higher, that is 1.3.1+X-blabla with a higher X.
>>
>
> Sorry for the delayed response.  I just setup Mercurial from source
> (much easier than expected...  :]  ) and it looks good (but you
> already knew that).  Thanks for the extremely quick response.  I'm
> impressed as usual.

Thanks a lot for the kind reply, I appreciate it! :-)

--
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.


_______________________________________________
Mercurial mailing list
Mercurial@...
http://selenic.com/mailman/listinfo/mercurial