On Thu, Mar 5, 2009 at 1:05 PM, Josef Wolf wrote: > On Wed, Mar 04, 2009 at 05:06:06PM -0500, Peter Harris wrote: >> >> I thought that this was already a part of svn, but it appears in the >> 1.6 (not quite final yet) release notes: "SSL client certificate >> passphrases can be stored in KWallet, GNOME Keyring, Mac OS Keychain, >> a Windows CryptoAPI encrypted form or in plaintext form." > > Ummm, I always found it hard to find their changelog. At least > http://svn.collab.net/viewvc/svn/trunk/CHANGES?view=markup&pathrev=36138 > don't mention those features. Do you have a pointer? http://subversion.tigris.org/svn_1.6_releasenotes.html#auth-related-improvements >> Of course, you're a paranoid admin, so you already have a >> pre-revprop-change hook in your svn server that prevents >> log/author/date changes. Right? ;-) > > Well, actually it allows the changes for a very limited user group (that > is: only me 8-). While I agree that author/date should not be changed, > I like to be able to fix silly typos in the log. After all, we all do > typos now and then ;-) True, but in my experience it happens considerably less often with git. I find and fix most of my typos when reviewing my change-set before doing a "git push" or "git svn dcommit". > Maybe there's room for more improvement: Since the merge is done on a > scratch branch anyway, why not letting the clones _push_ into branches > with random names: cloneX-`uuidgen` or something. So the clones could > do the push whenever they have net access. The actual merge can be done > completely decoupled from the push operation. Indeed. Or even not-so-random names, such as cloneX/topic-name if you prefer. Peter Harris -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
