List of suggestions

[Fabian Kreutz]

Saluton!

>> 1)
>> #      - changesets ancestral to the working directory::
>> #          hg log -f
>> -f means --follow, so what does "ancestral" mean in this case?

> It means that it follows the ancestors (of the working copy parent
> revision).

OK, so I stumbled over the non-existent connection between "ancestral"
and "follow". The example somehow implies that "-f" has the effect
of using the ancestral changesets.
But separately I can understand it:
  hg log -> without given revision -> all above current parent(s) = "ancestral"
  -f     -> follow over copies and renames


>> 2)
>> _admonitiontitles = {'attention': _('Attention:'),
>>                      'caution': _('Caution:'),
>>                      'hint': _('Hint:'),
>>                      'tip': _('Tip:'),
>> What is the difference between attention and caution; what between hint and tip?

> Hmm... maybe a native English speaker can explain the finer differences
> between the words. Btw, we only use '.. note::' in the code -- I added
> the other titles for compatibility with normal Docutils.

So is it then safe to translate them with the same word?

Also, I have seen this ".. note::", which I guess replaces an earlier "NOTE::".
Any guidelines for the translation of this?


> I also have new questions:
>
> 3)
> "the hook. ``eol.checkheadshook`` only checks heads, intermediate\n"
> "invalid revisions will be pushed. To forbid them completely, use the\n"
> 4)
> "diff trees from two commits"

OK, understood :)


>> 5)
>> "When you push a changeset that adds/modifies largefiles to a remote\n"
>> "repository, its largefile revisions will be uploaded along with it.\n"
>>
>> -> It's largefile revisions? So this will act in a distributed way and
>> send all revisions of the largefile? Or are we talking about the
>> remote *store*?

> The "largefile revisions" are the revisions of the largefiles changed in
> the revisions that are pushed. It will upload all revisions of the
> largefiles to the repo you push to.

It does? But then the push acts differently then the pull, doesn't it?
As I understood the pull, it will NOT fetch any actual largefile revisions
but postpone that until an update requires one.
So a push already pre-pushes all necessary versions of the largefile to
update to any revision into the remote repo?

Bye, Fabian

PS: And thanks for the quick answers :) I'm sure I'm successfully preventing
you from doing your job!