[PATCH] commands: add support for 'hg log -b .' (issue2078)

[Augie Fackler]

On Tue, Apr 13, 2010 at 9:17 AM, Benoit Boissinot <bboissin at gmail.com> wrote:
> On Tue, Apr 13, 2010 at 3:34 PM, Steve Losh <steve at stevelosh.com> wrote:
>> On Apr 13, 2010, at 7:23 AM, Sune Foldager wrote:
>>
>>> On 13-04-2010 01:59, Steve Losh wrote:
>>>> On Apr 12, 2010, at 7:56 PM, Matt Mackall wrote:
>>>>>
>>>>> I think this should be more generic. '-b .' should read as 'the branch
>>>>> that the working directory is on' so '-b<rev>' should similarly read as
>>>>> 'the branch<rev>' is on. In other words:
>>>>>
>>>>> branch = repo[rev].branch()
>>>>
>>>> What about:
>>>>
>>>> hg branch 123
>>>> ... commit ...
>>>> hg update default
>>>> hg log -b 123
>>>>
>>>> Would that list changesets in revision 123's branch or changesets in branch 123?
>>>
>>> Also, in case of hg incoming/pull, we really can't meaningfully interpret anything that isn't a branch (or . which is special cased), since we don't have the necessary information in the protocol.
>>
>> Technically 'pull -b .' would seem to mean "pull the branch that the remote is currently on" and you're right, that wouldn't be good because there's no way to tell.
>
> I always interpreted '.' as a local identifier. So I'd expect it to
> mean "pull the branch I'm currently working on."

+1, that's how I interpreted it as well.

>
> Benoit
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
>