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

RE: Subversion svn client doesn't show branch when checking in

From: Gale, David <David.Gale_at_Hypertherm.com>
Date: 2006-03-01 18:59:39 CET

Duncan Murdoch wrote:
> On 3/1/2006 12:09 PM, Gale, David wrote:
>> Ryan Schmidt wrote:
>>> 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? A branch in Subversion is absolutely nothing more
>>> than a plain directory. Whatever directory you checked out from (or
>>> subsequently switched to) is the one you're committing to.
>>
>> So, wouldn't it still be nice for svn to let you know which directory
>> (and repository) it's going to commit to? Might help prevent people
>> who've checked out a tag & forgotten to switch to a branch, for
>> instance...
>
> When you're using the command line client, there's no opportunity for
> it to question whether you really know what you're doing. When you
> say "commit this", it assumes you've already done "svn info" or
> whatever other checks you'll need.
>
> On the other hand, GUI clients like TortoiseSVN can be a lot
> friendlier, and in fact TSVN does tell you where the commit is going.
> So I'd suggest using TSVN, or whatever GUI works on your platform of
> choice.

Actually, there's plenty of time. It opens up an editor (vim, in my
case) for inputting a log message; it's got all the affected files
listed. If I notice a file I don't want to commit, or that it's missing
one I think should be there, I can exit out of the editor; if I haven't
typed anything in, it asks if I want to abort the commit. And, even
after that, it asks for my credentials (I don't have authentification
caching turned on), at which point I can still force an abort. (Yes, if
you pass the log message & any needed authentification credentials on
the command line, you don't have an opportunity; but if you're doing
that, then SVN has every right to expect you to know what you're doing.)

And, incidentally, my "platform of choice" (chosen by my company, not
me) is a *nix box with no windowing capability. It's command line or
nothing, in my case.

I'm just agreeing with the original poster that it'd be nice if the log
message window would present the path being committed to. Asking
developers to do an "svn info" just to find that out seems rather
unfriendly, don't you think?

-David

---------------------------------------------------------------------
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:24:33 2006

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