Point taken, I'll try to give an example of the functionality I'd like.
In short, I want 2 things:
1) Once changes are commited to the repository I want to be able to
export the list of files that were changed in the commit along with the
revision number that they were given upon committing them in Unified
2) When I right-click on my current working copy and select the "Show
Log" option, I would like to be able to export the list of changed in
the revision along with the actual revision number in Unified Diff format
Please note, I would just like to end up with a file containing a list
of the files to fetch from the repository as well as a list of files to
delete from the file system.
For instance, suppose that I have just made the following changes to my
Assuming that those changes were commited as revision 123, the Unified
Diff file I would like to be able to export in the situations described
above would look something along these lines:
--- my_project\API\classes\obsolete_class.php (revision 122)
+++ my_project\Database\my_master_script.sql (revision 123)
+++ my_project\API\classes\my_new_class.php (revision 123)
+++ my_project\API\classes\my_class.php (revision 123)
Using this output file I could upload the file to each server and have
the server fetch the patched files directly from the repository.
Does this example describe the desired functionality?
Stefan Küng wrote:
> Jona wrote:
>> Hmm.. think my explanation was too elaborate and the feature that I
>> wanted got lost in the process... so much for my grand schemes (the
>> ones that doesn't get lost in cyberspace that is)! :-)
>> I suppose what I really want is just a "do stuff" button which
>> extracts the list of files for a given version in Unified Diff format
>> as well as the actual version.
>> I.e. suppose I wanted to make a patch of revision 123, the Unified
>> Diff file would look like this:
>> +++ <PATH TO FILE ON SERVER> (revision 123)
>> It would be prudent to make the path to file relative to the top most
> What I meant with topmost folder was the to top folder in your working
>> Would it be possible to create such a functionality? Either as a
>> button or as a menu option.
> No. Because I'm getting more and more confused about what you want and
> why you want it.
> So please: try to explain what you want to do with those patches, what
> exactly is the work you want to have done. Don't try to explain _how_
> you think TSVN should do it, but really what you want to use it for.
> And please describe step by step what you want to do, best with an
> example of your working copy and the repository.
>> The same functionality seems to be archievable by using the "Show
>> Differences as Unified Diff" as you described, however this assumes
>> that you know the actual revision that the service you want to apply
>> the patch to is running (which you should, I know, am just saying... :-)
> Aeh, haeh? (translation: sorry, what???)
> The revision of the service (if you're talking of the running server)
> isn't of any interest to you. That has nothing to do with diffs.
>> The reason why I'd prefer the other is cause I'm lazy (show me a
>> programmer who isn't and I'll show you a liar) and don't want to
>> confirm all the merge changes on each of the servers I need to apply
>> the patch to.
>> Furthermore, once you've commited the changes from the working copy
>> to the repository you're not longer capable of creating a patch (the
>> file created is 0 bytes) and finally the save dialog for the "create
>> patch" option neglects to set the file type to .patch as
>> TortoiseMerge requires.
>> Is this on purpose(if so, I fail to see why?:-) or is it a bug?
> TortoiseMerge doesn't require the filetype ".patch". It also accepts
> ".diff" and any other filetype you choose (e.g. .txt").
> You mentioned something about multiple servers. Do you need your
> patches propagate your changes to all servers? Then have a look at svk:
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Aug 23 19:58:31 2004