[patch] limit log to a single branch
Dustin Sallings
dustin at spy.net
Sat Feb 9 13:19:31 CST 2008
Yeah, we actually close and reopen one of our branches a lot. I
checked the behavior with the coworker who was complaining about this
missing feature and he said it sounded right.
Mostly, we're just interested in seeing what's gone on recently as
a production push approaches. It would be interesting to know when
these reopen events occur, though. That may be as simple as
displaying something special when a parent has two children.
--
Dustin Sallings (mobile)
On Feb 9, 2008, at 10:57, "Stuart W. Marks" <smarks at smarks.org> wrote:
>
>
> Dustin Sallings wrote:
>> On Feb 8, 2008, at 20:36, Stuart W. Marks wrote:
>>> Yes, perhaps something like "svn log --stop-on-copy"? (For those
>>> of us reformed svn users.)
>>>
>>> For those of you who haven't had the misfortune of using svn, a
>>> "copy" operation creates a new branch in the repository. It's
>>> useful for viewing what changes have been made on this branch. For
>>> hg, maybe --stop-at-branch or some such would be a good name. This
>>> would additionally imply --follow.
>> The thing I implemented is closer to what people keep bugging me
>> to have around the office to do...just show the changelogs for a
>> single branch. It looks like this:
>> hg log -b stable
>> And we can see just the things that have been added to our
>> stable branch.
>
> Nice. I tried it out and it actually seems more useful than the --
> stop-on-copy thing I was proposing. Bryan's suggestion to rename it
> to --only-branch (as you implemented in your patch posted
> subsequently) is good too.
>
> Thanks!
>
> s'marks
>
>
More information about the Mercurial
mailing list