Eric Kow <[email protected]> writes:
> Again another case where it may have made sense to send the refactor
> and the new help separately
I guess I'm using the word "refactor" rather loosely. What each of
these patches does is threefold:
- Move text from literate comments to the foo_help string in Foo.lhs.
- Rewrite the literate comments to be clearer, and integrate them with
whatever was already in foo_help.
- Include option descriptions, use cases, caveats &c that were
conspicuous in their abscence. (For example, mentioning that
--checkpoint is currently useless on darcs-2 repos.)
The last one clearly isn't refactoring, and when I started it was the
least significant of the three. But the workflow I've settled into now
is to read the existing help, literate documentation and (superficially)
the code, then write a completely new foo_help string, then delete any
commentary it supersedes.
This workflow is working quite well for me, so I'm reluctant to change
it. I can name my patches differently in future
(e.g. s/Refactor/Rewrite/), but that probably doesn't help your issue:
> so that I can mindlessly apply one and then choose to hold off on
> another.
...and I'm not sure how useful it is to simply move text around and have
that change applied quickly, but the important rewriting work still
delayed as normal.
>> | The --lazy option isn't as useful for local copies, because Darcs will
>> | automatically use `hard linking' where possible. As well as saving
>> | time and space, you can move or delete the original repository without
>> | affecting a complete, hard-linked copy. Hard linking requires that
>> | the copy be on the same filesystem and the original repository, and
>> | that the filesystem support hard linking. This is usually the case,
>> | except for Windows versions prior to Vista.
>
> I don't think we have /any/ hard linking support for Windows, but I
> would heartily welcome a patch that provided it at least for Vista.
> Salvatore? I believe the request is on the bugtracker somewhere.
Nod; the source file has a FIXME comment to verify this.
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
