Stefan Küng <firstname.lastname@example.org> wrote on 22/06/2006 04:05:31 AM:
> May I suggest that this gets implemented with a right-drag operation?
> * get the source-tarball of the vendor tree
> * extract the vendor tree
> * select the vendor tree
> * right-drag the vendor tree to the correct working copy location
Right drag sounds fine.
> Then, TSVN would show up a dialog, then start comparing those two
> directory trees and the files in it. When the scanning is complete, show
> the 'result' in a list control like this:
> dst file status
> file1 modified
> file2 new
> file3 removed
> Then, ask the user if (s)he wants to apply those changes to the working
> copy. If yes, execute the corresponding commands (add/delete).
I hadn't considered comparing the trees before applying changes, but
it's obviously a good idea.
> I have no idea how you even want to find out if a file has been renamed
> in a vendor tree - usually that's nowhere documented, you just get a new
> version of the library.
Manual inspection of the modifications after the import. I haven't
ever used svn_load_dirs.pl but I think it presents some sort of list
of new verses deleted files and asks the user to line up those that
correspond to renamed files?
The more I think about it the less concerned I am about renames, at
the end of the day all it gains is slightly better log history for
directories that are generally imported from elsewhere anyway.
> Would be great if you could send in a patch for this!
I'll make a start in the next few days and see how I go.
> > 3. For bonus points I would also like to see the
> > equivalent functionality for the svn copies.
> Not sure what you mean by 'svn copies'. Can you explain?
Copying files from one part of a repository to another. Using either
'svn copy' or plain file overwrites.
My repository looks like this:
- Project1 - trunk - Source
- Library1 - Api
- Library1 - trunk - Source
- Distrib - Api
When a new version of the library is ready the headers and binaries
are commited in -Library1-trunk-Distrib. That directory then needs
to be mirrored into -Project1-trunk-Library1. It's not an svn
external because I want control over when the project upgrades to
the new version and I want the version to maintained when tagging
I haven't done this enough times to form a strong opinion whether
I'd prefer this to use 'svn copy' or just the right-drag operation
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Jun 24 09:52:04 2006