On Donnerstag, 8. November 2007, David Glasser wrote:
> On 11/7/07, Ph. Marek <philipp.marek@bmlv.gv.at> wrote:
> > On Mittwoch, 7. November 2007, C. Michael Pilato wrote:
> > > Blair Zajac wrote:
> > > > Currently svn_fs_copy() only allows you to copy a node from a
> > > > revision fs root into a txn fs root.
> > > >
> > > > Would it work in the BDB and FSFS backends with no code changes if we
> > > > allow copies from a txn fs root only if the destination fs root is
> > > > the same txn as the source fs root?
> >
> > I'd like to have that, too; in FSVS I'd like to avoid having two
> > revisions for a (copy, change) operation.
>
> Huh? You can copy and change in one revision... what exactly are you
> trying to accomplish?
Not if both are new files:
$ svnadmin create r
$ svn co file:///tmp/test/r wc
Checked out revision 0.
$ cd wc/
$ date > f1
/wc$ svn add f1
A f1
/wc$ svn cp f1 f2
svn: Cannot copy or move 'f1': it's not in the repository yet; try committing first
And that's (something like) my use-case ...
(User creates 5 new files - all with the same data. FSVS detect that
they're identical, and would like to link them in the repository to
save space).
Best of all would be supporting hardlinks (ie. taking the file-text) from
some arbitrary file in the repository (issue 2286,
http://subversion.tigris.org/issues/show_bug.cgi?id=2286), but solving the
copyfrom to the current revision would be a first step in that direction -
and would solve the same problem for linking later.
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 8 09:11:44 2007