On Tue, Jun 2, 2009 at 11:46 AM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
>
> In a commit, svn first sends the operation requests to the repository,
> so the repo can verify that every operation is possible/allowed. After
> that part is done, the content changes are sent. It wouldn't make much
> sense to send the contents right away (especially if the content changes
> are several MB big), only to have the commit get rejected in the last
> change because a file was outdated or an added file already exists in
> the repository or the user doesn't have write access to a particular
> folder.
>
> I've just tested a commit with two added files and three modifications:
> the "sending content" was also shown for the added files.
> But of course, if the added files were actually renamed/moved (i.e., an
> add with a corresponding delete), then "sending content" won't be
> necessary because the action/command (i.e., move/rename) is enough and
> no content has to be sent.
No, these files were physically added. They never existed in the repository
beforehand. Did I find a bug?
PS: Why is it showing my name as 'void pointer'? It does this on the SVN
mailing list too. It's an alias I use in various other places, but not on
any of my mailing list subscriptions. I can't figure out where it is pulling
that name from.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2358852
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-02 20:04:57 CEST