Richard Lowe wrote:
> Vladimir Kotal writes:
>> or something more complicated ?
>>
>> Don't know why but any addition to the customized file does not have
>> any effect on 'hg outgoing -v' output. In fact, there is no attempt to
>> open the style file in 'truss -f hg outgoing -v'.
>
> You adde
Richard Lowe wrote:
> Vladimir Kotal writes:
>
>> Vladimir Kotal wrote:
>>
>>
>>
It is, jmcp asked me about this last night too. You can adjust the
style to insert \n's after each file.
>>> Any example on how to achieve that ?
>
> You can do it by customizing the style used.
>
> cp
Vladimir Kotal wrote:
>> It is, jmcp asked me about this last night too. You can adjust the
>> style to insert \n's after each file.
>
> Any example on how to achieve that ?
It's possible to hack Mercurial and Cadmium to do that but it is not nice:
0. enable cadmium in ~/.hgrc
1. inse
Vladimir Kotal writes:
> Richard Lowe wrote:
>> Vladimir Kotal writes:
>>
>>> Vladimir Kotal wrote:
>>>
>>>
>>>
> It is, jmcp asked me about this last night too. You can adjust the
> style to insert \n's after each file.
Any example on how to achieve that ?
>>
>> You can do it by
Vladimir Kotal writes:
> Vladimir Kotal wrote:
>
>
>
>>> It is, jmcp asked me about this last night too. You can adjust the
>>> style to insert \n's after each file.
>>
>> Any example on how to achieve that ?
>
You can do it by customizing the style used.
cp
/usr/lib/python2.4/vendor-package
> >> Also, 'hg outgoing' could do with some line wrapping (one file per
> >> line ?) for better readability. Maybe that's doable with the
> >> --template/--style' options somehow ?
> >
> > It is, jmcp asked me about this last night too. You can adjust the
> > style to insert \n's after each file.
Richard Lowe wrote:
> Right, list' is a cdm command, it's printing out what cdm knows.
> 'outgoing' is from Hg, and doesn't need to go as far as cdm does.
Interesting, it would seem just the opposite given that cdm is built
atop hg modules. On the other hand it seems logical since 'hg outgoing
Richard Lowe wrote:
> It's probably preserving the rename (which is what 'workspace filerm'
> and 'wx rm' effectively do), rather than special casing deleted_files
> into an 'hg rm'.
>
> You should not re-create deleted_files in a mercurial gate.
so the 'deleted_files' directory in the gate is
Hi all,
It looks like wx2hg converts files deleted in Teamware workspace as
added files in Mercurial workspace (added to 'deleted_files' directory).
e.g. part of the following 'hg list' snippet:
---
added:
deleted_files/usr/src/cmd/ssh/include/strsep.h (renamed from
usr/src/cmd/ssh/i
Vladimir Kotal writes:
> Richard Lowe wrote:
>
>
>
>> It's probably preserving the rename (which is what 'workspace filerm'
>> and 'wx rm' effectively do), rather than special casing deleted_files
>> into an 'hg rm'.
>>
>> You should not re-create deleted_files in a mercurial gate.
>
> so the 'd
Vladimir Kotal writes:
> Hi all,
>
> It looks like wx2hg converts files deleted in Teamware workspace as
> added files in Mercurial workspace (added to 'deleted_files' directory).
>
> e.g. part of the following 'hg list' snippet:
>
> ---
> added:
> deleted_files/usr/src/cmd/ssh/include/
11 matches
Mail list logo
