Re: Confusing commit log status

void pointer wrote:
> I have to admit, this has always been confusing ever since I used
> TortoiseSVN in early v1.4 days.
>
> Below I have pasted part of a commit log status for a single commit.
> Note that there are both Added and Modified files. Notice that the
> "Sending Content" status only shows modified files, however it does not
> show that content is being sent for "added" files. To be honest, I'm not
> even really sure why "Sending Content" exists, since when I see
> "Modified" in my commit log message, I would think that is the point
> where the data is being verified and sent to the server.
>
> Can someone explain this? Thanks.

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.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2358829
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].