Tickets :: Comment on [#5284] Move to subversion for Horde code repository

* Your Email Address
* Spam protection	Enter the letters below: .__ .__ .___. .. . \| \\| \[__ \| \|\|\/\| \|__/\|__/\| \|__\|\| \|
Comment	>> On commit emails: > >> I think inline text-only diffs with a max message size would be > >> ideal. I agree about colored diffs and I also really hate systems > >> that send out commit messages over a megabyte. I think if we can do > >> it, something that sends a main body part with the log message and > >> chora links, and then inline attachments of type text/diff for up to > >> 40k or so of changes, seems nice. > > > > Sounds good. > > > >> On checking modules out inside other modules: > >> The svn way to do this is with externals, BUT: there is no way to > >> commit to everything at once using externals (per > >> http://svn.haxx.se/users/archive-2007-01/0955.shtml). The ideal > > > > And this has always been the show stopper for me to switch Horde to > SVN. I had hopes that this could properly be dealt with in the > meantime. > > > >> situation here is that we would have a tree of apps that didn't need > >> to be in the webroot, so we wouldn't need to put them inside each > >> other. Externals is a reasonable solution that would let us have a > >> dev tree and just commit to modules separately. Another option is > >> symlinks, which subversion can handle now - we could put links to the > >> apps inside the horde/ module, assuming they were now on the same > >> level as horde. > >> > >> One side effect of having different developer and anonymous URLs > >> (https vs http) is that if we want to use externals on our own stuff, > >> it has to be different sets of externals properties for dev and anon. > > > > That sounds awkward.
Attachment
Watch this ticket

Saved Queries