Re: allow C-x v i / C-x v v to create a repository if none is available

[Dan Nicolaescu <dann@ics.uci.edu>]

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

  > > When doing C-x v i or C-x v v on an unregistered file that is in a
  > > directory not under any version control, the file will be registered
  > > with RCS.  That is not exactly what most users want.
  > 
  > Very good point.  In the past, there wasn't much choice anyway since
  > creating a CVS repository required a lot more work, but indeed, with
  > current DVCS such a behavior makes sense again.
  > 
  > Now, most relevant backends will also want to know where you want to put
  > the root of your new repository.  Should we let the backend function
  > `create-repo' prompt for this, or should we move it to the generic part
  > of the code?  You seem to have taken the first choice, whereas I'd lean
  > towards the second.

I just took smallest patch path :-), just create the repository in the
current directory.

Do we have any backend specific function that are required to prompt?
I don't think we do.

So I'd say that for consistency it would be better to prompt in the
generic code.  This also avoid the code duplication in all backends.

What's your reasoning for leaning towards the second?