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

Re: Porting Subversion to EBCDIC

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-02-10 23:46:03 CET

Mark Phippard <MarkP@softlanding.com> writes:

> > I have no problem with setting up such a branch for you, as long as
> > "catching up" is done in reasonably sized chunks of work, not one or
> > two strings at a time.
> I think I mean two different things.

Sorry. I was being unnecessary non-verbose.

> 1) Since we are working on the branch, just switching to trunk will be a
> lot of work. Since I am currently using svk to mirror, and I didn't mirror
> the whole repository, it will be a pain now to set that up. I would rather
> just start working in the real repository.

I'm having the darnedest time parsing this.

Allow me to be more verbose about what I was thinking:

   - Make a branch in the main Subversion repository (at
     svn.collab.net) based on the 1.1.x branch. Call the branch

   - Grant partial commit access (to the branch only) for you and your

   - Watch as you plunk that massive diff file atop your new branch
     and commit up.

   - Poof. Now you can start managing your branch like the locking

I want only to avoid the rest of the community getting 50 commit
mails/day with tiny little iterative changes that could have been
grouped together into larger sets.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 10 23:49:19 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.