On Thu, Apr 26, 2007 at 11:28:22AM -0400, Terry Smith wrote: > >probably this is known to every old darcs user: if you push a patch > >to a > >remote repo which is accessible by others, then it's really bad to > >unrecord/unpull that patch > > > >though newbies (to darcs) regularly do so and afaik there is no way to > >prevent this > > > >so the questions are: > > > >1) is there any way to do so? > >2) if not, should i sent a feature request about having a --no-remote > >(or something like that) option for unrecord/unpull? > > You can edit _darcs/prefs/defaults on the remote repo to disable > certain commands. > > For example, the following disables the unpull and unrecord commands. > > >$ cat _darcs/prefs/defaults > >unpull disable > >unrecord disable
I think there was a wish-list item in the old bug tracker (RT) a long time ago, for options to the Initialize command (and Get and Put) to automatically set up the new repo with suitable defaults, such as some commands disabled. Something like --master-repo (with most commands disabled and not allowing any conflicts), --normal-repo (a default, with dangerous "expert" commands disabled) and --working-repo (with everything enabled). The names of the options are just suggestions. -- Tommy Pettersson <[EMAIL PROTECTED]> _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
