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

Re: gcc source management requirements

From: Peter Davis <peter_at_pdavis.cx>
Date: 2002-12-10 05:40:39 CET

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 09 December 2002 20:20, Robert W Anderson wrote:
> Can I create "my own branch" in Subversion if I don't have write access
> to the repository? From what I've read it seems like the answer is no,
> but I'm trying to reconcile this with this "very easy" claim:
> Contacting someone by email and convincing them that I'm trustworthy
> enough to grant write access can be anything but easy.

That's a completely different subject: from what I understand, microbranches
are useful for resolving conflicts during a commit, which implies that you
already have commit access.

You are talking about remote repositories, where you create your own
repository down-stream from the "official" repository, and the two
repositories can merge change-sets back and forth between each other.
Subversion doesn't do this (BitKeeper does), but it might some day.

I do claim that creating branches in Subversion is "very easy", but I never
made any claims that you can create your own branch without write access.
That's an issue that has already been discussed on this list and will be
raised again in the future. CVS can't do it, and Subversion won't either for
the time being. For now, use "svn diff | mail".

- --
Peter Davis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE99XBHhDAgUT1yirARAg1rAJ94KFnU/OG2dgZ/PNZFtDQX5pFdvgCeMyXl
OjBjfBxa6W1DET/jSPsRWFM=
=dVEL
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 10 05:41:21 2002

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.