[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Another VC terminology change?
From: |
Dan Nicolaescu |
Subject: |
Re: Another VC terminology change? |
Date: |
Fri, 12 Oct 2007 08:23:51 -0700 |
Stefan Monnier <address@hidden> writes:
> >> Not about "checkout" which sometimes means "update" and sometimes "get".
> > Speaking of "update", vc-update needs to be rethought a bit.
> > Mercurial, bzr and git (maybe other systems too) don't seem to want to
> > do merges based on a file, but on changesets.
> > What should we do about that?
>
> Those backends should simply signal an error if requested to update
> something less than the whole tree.
So what would the UI be for that?
vc-BACKEND-merge-news currently has a `file' parameter.
Should backends check if it is a directory, and then run the merge
command?
Who is responsible for updating all the buffers for files that have
been changed by the merge?
- Another VC terminology change?, Eric S. Raymond, 2007/10/11
- Re: Another VC terminology change?, Dan Nicolaescu, 2007/10/11
- Re: Another VC terminology change?, Stefan Monnier, 2007/10/11
- Re: Another VC terminology change?,
Dan Nicolaescu <=
- Re: Another VC terminology change?, Stefan Monnier, 2007/10/12
- Re: Another VC terminology change?, Dan Nicolaescu, 2007/10/12
- Re: Another VC terminology change?, Stefan Monnier, 2007/10/12
- Re: Another VC terminology change?, Dan Nicolaescu, 2007/10/12
- Re: Another VC terminology change?, Stefan Monnier, 2007/10/12
Re: Another VC terminology change?, Richard Stallman, 2007/10/11