[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Managing my patch collection and svn sessions

From: Gabriela Gibson <gabriela.gibson_at_gmail.com>
Date: Fri, 23 Aug 2013 20:26:44 +0100

I'm looking at my hoard of patches and log messages in my
~/patches directory, and it's large and not really all that

Still, it's not really something I'd want to delete, even failed
attempts and odd snippets are often useful to keep around.

In a way it's a bit ironic to contribute code to a VCS but to
hoard patches, notes and log messages like it's 1995, I'm sure I
must be doing it wrong.

How do you keep your local patch collection organised? Or did you
find that old patches are not really useful to you?

I did try keeping various trunks, but this brought other problems, so
I don't anymore, what I do if I need to switch is to take a patch and
revert the 'working' trunk, and apply the patch for the other project.

I'd really like a program that takes care of managing my svn work
sessions with different projects.

So, say I want to swap my current session of project A with session N
of the project B I worked on last week:

* stash the current workspace of my session on project A (patch,
history, notes, etc)
* fetch the correct trunk/branch revision pertaining to loaded session
of project B
* apply the patch of the selected session of project B.
* restore my shell history of that session (or entire project)
* show me the notes I kept for that session, or if I ask, all the
   notes of sessions of project B

Is there such a tool? Maybe I just need a better way of keeping house?
Received on 2013-08-23 21:27:17 CEST

This is an archived mail posted to the Subversion Dev mailing list.