[PATCH 1 of 1] churn: improve description
timeless
timeless at gmail.com
Wed Jun 17 15:00:54 CDT 2009
On Wed, Jun 17, 2009 at 10:52 PM, Cedric Duval<cedricduval at free.fr> wrote:
> timeless wrote:
>> > bookmarks Mercurial bookmarks
>
>> > "track a line of development with moving pointers"?
>
>> I don't like 'pointers' but can't offer something better
>
> markers?
maybe?
>> > convert converting foreign VCS repositories to Mercurial
>
>> > s/converting/convert/ ?
>
>> to => into ?
>> convert => import from ?
>
> Perhaps, though within Mercurial the word 'import' usually carries the
> semantics of adding into an existing repository (import/qimport
> commands), while here a whole new repository may be created during the
> process (incremental additions can be ignored for the sake of this
> headline).
in English, you can import something new or into an existing thing,
and the concept of importing foreign objects isn't uncommon. But I'm
interested in other opinions.
> "turn a foreign or native VCS repository into a Mercurial one"?
>
> Not happy about that either, but perhaps throwing thoughts will get
> us somewhere eventually. :)
I'm definitely not happy w/ this :)
> "create a repository from another one (foreign VCS or native)"?
nor this :(
>> > hgcia CIA notification
>
>> > "integrate Mercurial with the CIA notification service"?
>
>> the => a ? (is there *ONLY* one CIA in the whole world, or is it
>> something for which many people can run their own instances?)
>
> It is GPL, so I guess people could spawn their own. Whether that
> happens, no idea.
I don't mean fork the code base, I mean is CIA the same CIA bot
process I see on freenode as well as in other random places?
>
>> > inotify inotify-based status acceleration for Linux systems
>
> "speed up status using OS facilities"?
I think for now I'm fine w/ leaving this alone. We can worry about it
once it actually does what I thought it did (I think I got confused by
reading about future work).
More information about the Mercurial-devel
mailing list