All patches and comments are welcome. Please squash your changes to logical
commits before using git-format-patch and git-send-email to
patches@git.madduck.net.
If you'd read over the Git project's submission guidelines and adhered to them,
I'd be especially grateful.
This kind of thing is why I shouldn't commit changes before lunch. But do I wait for lunch before committing stupid logic errors? Noo..
* Fix a bug caused by a stupid typo.
* Add the -n switch, for disabling recursion.
* Fix a bug caused by a stupid typo.
* Add the -n switch, for disabling recursion.
- -- Joey Hess <joeyh@debian.org> Thu, 18 Oct 2007 15:18:40 -0400
+ -- Joey Hess <joeyh@debian.org> Thu, 18 Oct 2007 15:27:01 -0400
mr (0.3) unstable; urgency=low
mr (0.3) unstable; urgency=low
-If the "skip" parameter is set and its command returns nonzero, then B<mr>
+If the "skip" parameter is set and its command returns true, then B<mr>
will skip acting on that repository. The command is passed the action
name in $1.
will skip acting on that repository. The command is passed the action
name in $1.
-If the "chain" parameter is set and its command returns nonzero, then B<mr>
+If the "chain" parameter is set and its command returns true, then B<mr>
will try to load a .mrconfig file from the root of the repository. (You
should avoid chaining from repositories with untrusted committers.)
=item deleted
will try to load a .mrconfig file from the root of the repository. (You
should avoid chaining from repositories with untrusted committers.)
=item deleted
-If the "deleted" parameter is set and its command returns nonzero, then
+If the "deleted" parameter is set and its command returns true, then
B<mr> will treat the repository as deleted. It won't ever actually delete
the repository, but it will warn if it sees the repository's directory.
This is useful when one mrconfig file is shared amoung multiple machines,
B<mr> will treat the repository as deleted. It won't ever actually delete
the repository, but it will warn if it sees the repository's directory.
This is useful when one mrconfig file is shared amoung multiple machines,
elsif ($? & 127) {
print STDERR "mr $action: deleted test received signal ".($? & 127)."\n";
}
elsif ($? & 127) {
print STDERR "mr $action: deleted test received signal ".($? & 127)."\n";
}
- if ($ret >> 8 == 0) {
- print STDERR "mr error: $dir should be deleted yet still exists\n\n";
- push @failed, $dir;
- return;
- }
+ }
+ if ($ret >> 8 == 0) {
+ print STDERR "mr error: $dir should be deleted yet still exists\n\n";
+ push @failed, $dir;
+ return;
print STDERR "mr $action: skip test received signal ".($? & 127)."\n";
exit 1;
}
print STDERR "mr $action: skip test received signal ".($? & 127)."\n";
exit 1;
}
- if ($ret >> 8 == 0) {
- print "mr $action: $dir skipped per config file\n" if $verbose;
- push @skipped, $dir;
- return;
- }
+ }
+ if ($ret >> 8 == 0) {
+ print "mr $action: $dir skipped per config file\n" if $verbose;
+ push @skipped, $dir;
+ return;