Andrew Haley wrote:
>Ryan Schmidt writes:
> > On Mar 1, 2006, at 15:10, Andrew Haley wrote:
> >
> > > When I do a commit, svn doesn't tell me which branch I'm committing
> > > to. So, when I check in the log, I have no way to know which files
> > > I'm about to overwrite. This is a regression from CVS, which does
> > > tell me which branch I'm committing to.
> >
> > Subversion does branching completely differently than CVS. Have you
> > read the book?
>
>Yes.
>
> > A branch in Subversion is absolutely nothing more than a plain
> > directory.
>
>Yes.
>
> > Whatever directory you checked out from (or subsequently switched
> > to) is the one you're committing to.
>
>The same is true of CVS, but it displayed the real place that the
>files were being committed to.
>
>When I type a commit message for gcc.c, I need to know that it's gcc.c
>on my experimental branch, not in the trunk. With CVS, I could tell
>that, but with svn I can't. And it's nothing to do with Subversion
>per se, it's just the svn client.
>
>It's nothing to do with the way that svn works internally, because the
>simple patch that I attached changes svn to provide all the
>information that CVS did.
>
>So, what is the advantage of hiding the destination URL for the files?
>
>Andrew.
>
Agreed. SVN should at least have a way of displaying complete paths in
the commit message template (this has gotten me in trouble a number of
times when doing imports- though for checkins you could use svn info)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 1 19:02:01 2006