Sat Nov 12 11:00:06 GMT 2005 Dave Love <[EMAIL PROTECTED]>
* English and markup fixes.
New patches:
[English and markup fixes.
Dave Love <[EMAIL PROTECTED]>**20051112110006] {
hunk ./Add.lhs 84
-one only in case. This is because the HFS+ file system used on under MacOS
+one only in case. This is because the HFS+ file system used on MacOS
hunk ./Annotate.lhs 104
-fully in the 'common options' portion of the manual.
+fully in the `common options' portion of the manual.
hunk ./Annotate.lhs 146
-If a patch name and a directory are given, these details are given for the time after
-that patch was applied will be output. If a directory and a tag name are given, the
+If a patch name and a directory are given, these details are output for the time after
+that patch was applied. If a directory and a tag name are given, the
hunk ./Apply.lhs 235
-the patch was gpg-signed by a key which is in \verb!PUBRING!, and will
+the patch was GPG-signed by a key which is in \verb!PUBRING!, and will
hunk ./Apply.lhs 272
-If you give the \verb!--reply FROM! option to darcs apply, it will send the
+If you give the \verb!--reply FROM! option to \verb!darcs apply!, it will send the
hunk ./Apply.lhs 279
-address not be the same as the address at which the patch was received in
+address not be the same as the address at which the patch was received, in
hunk ./Apply.lhs 309
-the patch will be forwarded to you. Please (for your own sake!) be certain
+the patch will be forwarded to you. Please (for your own sake!)\ be certain
hunk ./Apply.lhs 371
-used to override an interactive or gui which might be set in your
+used to override an \verb!interactive! or \verb!gui! which might be set in your
hunk ./Apply.lhs 381
-If you want to use a command different from the default one for sending mails,
-you need to specify a commandline with the \verb!--sendmail-command! option.
-The commandline can contain the format specifier \verb!%t! for to
+If you want to use a command different from the default one for sending mail,
+you need to specify a command line with the \verb!--sendmail-command! option.
+The command line can contain the format specifier \verb!%t! for to
hunk ./Apply.lhs 452
- "key, or there was a gpg failure.\n"
+ "key, or there was a GPG failure.\n"
hunk ./Apply.lhs 488
-of the test are send in the reply email. You can also specify the
+of the test are sent in the reply email. You can also specify the
hunk ./ArgumentDefaults.lhs 68
-If you would like a command to be run everytime patches are recorded
+If you would like a command to be run every time patches are recorded
hunk ./ArgumentDefaults.lhs 79
- be added to the repository with \verb!darcs add!, doing so would
+ be added to the repository with \verb!darcs add!; doing so would
hunk ./Changes.lhs 55
-changes_description = "Gives a changelog style summary of the repo history."
+changes_description = "Gives a changelog-style summary of the repo history."
hunk ./Changes.lhs 61
- "Changes gives a changelog style summary of the repo history,\n"++
+ "Changes gives a changelog-style summary of the repo history,\n"++
hunk ./Changes.lhs 103
-those patches which affect those files or the contents of those directories, or
-of course the directories themselves. This includes changes that happened to
+those patches which affect those files or the contents of those directories or,
+of course, the directories themselves. This includes changes that happened to
hunk ./Changes.lhs 204
-information which will allow the current state of the repository to be
+information to allow the current state of the repository to be
hunk ./DarcsArguments.lhs 464
-e.g.\ ``David Roundy <[EMAIL PROTECTED]>''. The easiest way to do
+e.g.\ \verb!David Roundy <[EMAIL PROTECTED]>!. The easiest way to do
hunk ./DarcsArguments.lhs 474
-Also, a global author file can be created with the name
-\verb!.darcs/author! in your home directory. This file overrides the
+Also, a global author file can be created in your home directory with the name
+\verb!.darcs/author!. This file overrides the
hunk ./DarcsArguments.lhs 717
-The \verb!--dry-run! option will cause darcs to not actually take the specified
-action. but only print what would have happened. Not all commands accept
+The \verb!--dry-run! option will cause darcs not to actually take the specified
+action, but only print what would have happened. Not all commands accept
hunk ./DarcsArguments.lhs 724
-The \verb!--summary! show a summary of the patches that would have been
+The \verb!--summary! option shows a summary of the patches that would have been
hunk ./DarcsArguments.lhs 994
-To provide a command that should be run when even a darcs command completes
-successfully, use \verb!--posthook! to give the command. This is useful in
+To provide a command that should be run whenever a darcs command completes
+successfully, use \verb!--posthook! to specify the command. This is useful
hunk ./DarcsArguments.lhs 1027
+
hunk ./DarcsCommands.lhs 66
-is, the named patches which other users can pull), some commands only
+is, the named patches which other users can pull); some commands only
hunk ./DarcsRepo.lhs 27
-you view them with an editor (e.g. vi or emacs), that editor may create
+you view them with an editor (e.g.\ vi or Emacs), that editor may create
hunk ./DarcsRepo.lhs 163
-been recorded, and cannot be determined by a simple diff. For example file
+been recorded, and cannot be determined by a simple diff. For example, file
hunk ./DiffCommand.lhs 118
-Currently it is hardwired to "diff".
+Currently it is hardwired to ``diff''.
hunk ./Optimize.lhs 112
-transfered (only the most recent inventory). It also because it gives a
+transfered (only the most recent inventory). It also gives a
hunk ./Optimize.lhs 130
-If you use the \verb!--checkpoint! option optimize creates a checkpoint patch
+If you use the \verb!--checkpoint! option, optimize creates a checkpoint patch
hunk ./Optimize.lhs 197
-disk space, which translates into less bandwidth if repository is accessed
-remotely. Note that patches will always have the ".gz" extension whether
+disk space, which translates into less bandwidth if the repository is accessed
+remotely. Note that patches will always have the ``.gz'' extension whether
hunk ./Optimize.lhs 207
-\verb!--dont-compress! means "don't compress, but don't uncompress
-either". It would be useful if one of the compression options was provided
+\verb!--dont-compress! means ``don't compress, but don't uncompress
+either''. It would be useful if one of the compression options was provided
hunk ./Optimize.lhs 305
-ordering of it's internal patch inventory. This may help to produce shorter
-'context' lists when sending patches, and may improve performance for some
+ordering of its internal patch inventory. This may help to produce shorter
+`context' lists when sending patches, and may improve performance for some
hunk ./PatchChoices.lhs 48
-force_last tells PatchChoices that a particular patch is required to be in
+\verb!force_last! tells PatchChoices that a particular patch is required to be in
hunk ./PatchChoices.lhs 53
-asked for the final output (e.g.\ by get_first_choice). Instead, each
+asked for the final output (e.g.\ by \verb!get_first_choice!). Instead, each
hunk ./PatchChoices.lhs 55
-undecided--undecided leans towards ``middle''. In case you're wondering
+undecided---undecided leans towards ``middle''. In case you're wondering
hunk ./PatchMatch.lhs 87
-darcs repositories (e.g. cgi scripts like viewCVS).
+darcs repositories (e.g.\ CGI scripts like viewCVS).
hunk ./Push.lhs 150
-\verb!darcs!, i.e., the darcs executable must be in the default path on
+\verb!darcs!, i.e.\ the darcs executable must be in the default path on
hunk ./Record.lhs 445
-extend until the end of file of stdin is reached (ctrl-D on unixy systems).
+extend until the end of file of stdin is reached (ctrl-D on Unixy systems).
hunk ./Record.lhs 447
-repository conversion scripts. The prompts are intended mostly as useful
+repository conversion scripts. The prompts are intended mostly as a useful
hunk ./Record.lhs 455
-By default, \verb!record! works interactively. Probably you only thing you need
-to know about using this is that you can press \verb!?! at the prompt to be shown
-a list of the rest the options and what they do. The rest should be clear from there. Here's a
+By default, \verb!record! works interactively. Probably the only thing you need
+to know about using this is that you can press \verb!?! at the prompt to be
+shown a list of the rest of the options and what they do. The rest should be
+clear from there. Here's a
hunk ./RepoPrefs.lhs 69
-e.g.\ ``David Roundy <[EMAIL PROTECTED]>''. This
+e.g.\ \verb!David Roundy <[EMAIL PROTECTED]>!. This
hunk ./Send.lhs 178
-If you want to create a patches having context, you can use the
+If you want to create patches having context, you can use the
hunk ./Send.lhs 287
-expects the complete mail on standard input. E.g. the commandlines for evolution
+expects the complete mail on standard input. E.g.\ the commandlines for evolution
hunk ./SetPref.lhs 52
-merges is perform, you may end up with a different final prefs
+merges is performed, you may end up with a different final prefs
hunk ./Tag.lhs 140
-Because the word 'tagged' is always prepended to the tag name, you can search
+Because the word `tagged' is always prepended to the tag name, you can search
hunk ./Test.lhs 36
-``test'' value to be a command to run. e.g.
+``test'' value to be a command to run, e.g.
hunk ./Unrecord.lhs 70
-the change from the working copy too (where they otherwise will show
+the changes from the working copy too (where they otherwise will show
hunk ./Unrecord.lhs 115
-These options can be slow if the list of patches to match with is long,
+These options can be slow if the list of patches to match is long,
hunk ./Unrecord.lhs 228
-to used unpull. If the patch was originally from another repo, then
+to use unpull. If the patch was originally from another repo, then
hunk ./Unrecord.lhs 296
- "Beware that you can lose precious code by obliterateing!\n"
+ "Beware that you can lose precious code by obliterating!\n"
hunk ./Unrecord.lhs~ 97
-and almost never would you want to unrecord changes before a tag---you
-would have to unrecorded the tag as well to do that.
+and almost never would you want to unrecord changes before a tag
+(you would have to have unrecorded the tag as well to do that).
hunk ./WhatsNew.lhs 60
-\haskell{whatsnew_help} Darcs whatsnew will return a non-zero value if
+\haskell{whatsnew_help} \verb!darcs whatsnew! will return a non-zero value if
hunk ./WhatsNew.lhs 199
-If you give one or more file or directory names as an argument to whatsnew,
-darcs whatsnew will output only changes to those files or to files in those
-directories.
+If you give one or more file or directory names as an argument to
+\verb!whatsnew!, darcs will output only changes to those files or to files in
+those directories.
hunk ./darcs-createrepo.lhs 31
-that user up to recieve and validate patches by email. Because
+that user up to receive and validate patches by email. Because
hunk ./darcs-createrepo.lhs 39
-case, you'll need to add a few users' gpg keys to this file with gpg's
+case, you'll need to add a few users' GPG keys to this file with GPG'S
}
Context:
[add a few more changelog entries.
David Roundy <[EMAIL PROTECTED]>**20051111133638]
[fix bug in code for external conflict resolution.
David Roundy <[EMAIL PROTECTED]>**20051111132557]
[spelling fix in docs.
David Roundy <[EMAIL PROTECTED]>**20051111123035]
[use substrPS for more robust searching for the patch bundle hash.
David Roundy <[EMAIL PROTECTED]>**20051110145918]
[speed up replace by first checking on each line if there might be a match.
David Roundy <[EMAIL PROTECTED]>**20051110143047
The idea is that if there is no substring match, there won't be a token
match, and we can save huge amounts of time. On my very simple test
(replacing if with fi in all of darcs' files), the speedup took us from 30
seconds to 3 seconds to pull.
]
[implement FastPackedString.substrPS, which searches for a substring.
David Roundy <[EMAIL PROTECTED]>**20051110140311]
[make pull.pl work on MacOS X using ugly hack.
[EMAIL PROTECTED]
For some reason ghc on MacOX X gives an Unknown error 0 where it ought to
give a "permission denied" error. This change just makes us recognize this
and turns the test failure into a TODO check.
]
[add a couple of changelog entries.
David Roundy <[EMAIL PROTECTED]>**20051108132617]
[make sftp honor the SSH_PORT env variable.
David Roundy <[EMAIL PROTECTED]>**20051108131847]
[Fix spurious failure of the revert test case
Florian Weimer <[EMAIL PROTECTED]>**20051107195237
"darcs revert -a" does not require confirmation.
]
[Check for excess input in test cases
Florian Weimer <[EMAIL PROTECTED]>**20051107195045
This change also fixes a latent race condition (by adding a call to
waitpid): darcs might not have run to completion when echo_to_darcs
returns.
]
[During tests, do not exit silently when a write fails
Florian Weimer <[EMAIL PROTECTED]>**20051107194913]
[Avoid putting a wrongly-named directory in dist tarball if the name we wanted already exists in $TMPDIR
Simon McVittie <http://www.pseudorandom.co.uk/>**20051106145821]
[fix example in doc to work with version 1.0.3 and above
Tommy Pettersson <[EMAIL PROTECTED]>**20051106232940
Discovered and fix suggested by Pavel Pisa.
]
[update version number to 1.0.4rc3.
David Roundy <[EMAIL PROTECTED]>**20051108120613]
[TAG 1.0.4rc2
David Roundy <[EMAIL PROTECTED]>**20051106121631]
Patch bundle hash:
ad5b77df34413c49f6830a29a2047601c2850380
_______________________________________________
darcs-devel mailing list
[email protected]
http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel
