On Nov 30, 2006, at 00:43, Paul Duran wrote:
> One of my colleagues was committing files last night and it was saying
> they committed successfully however some of the files in the
> revision do
> not appear to have been committed. The revision log shows them as
> committed but the log for an individual file does not show that
> revision.
>
> It has occurred multiple times in the past couple of days.
>
> As an example,
>
> we have a revision : 1089 that contains changes to two files:
>
> D:\projects\BMS_prj_tasks\source\Oasis.BMS\Oasis.BMS.UI\Task>svn log
> -r1089 -v
> ----------------------------------------------------------------------
> --
> r1089 | AClark | 2006-11-30 16:10:48 +1100 (Thu, 30 Nov 2006) | 3
> lines
> Changed paths:
> M
> /branches/prj_tasks/source/Oasis.BMS/Oasis.BMS.UI/Task/TaskSearch.aspx
> M
> /branches/prj_tasks/source/Oasis.BMS/Oasis.BMS.UI/Task/UserControls/
> Task
> Details.ascx
>
> (Updated HTML missed during the SVN issues)
> - Add Department drop down to Search page, modify to conform to BMS UI
> standards
> - Modify TaskDetails.ascx to conform to BMS UI standards
> ----------------------------------------------------------------------
> --
>
>
> If I try to view the log for each of those files individually using
> this
> revision number:
>
> D:\projects\BMS_prj_tasks\source\Oasis.BMS\Oasis.BMS.UI\Task>svn log
> -r1089 -v TaskSearch.aspx
> ----------------------------------------------------------------------
> --
> r1089 | AClark | 2006-11-30 16:10:48 +1100 (Thu, 30 Nov 2006) | 3
> lines
> Changed paths:
> M
> /branches/prj_tasks/source/Oasis.BMS/Oasis.BMS.UI/Task/TaskSearch.aspx
> M
> /branches/prj_tasks/source/Oasis.BMS/Oasis.BMS.UI/Task/UserControls/
> Task
> Details.ascx
>
> (Updated HTML missed during the SVN issues)
> - Add Department drop down to Search page, modify to conform to BMS UI
> standards
> - Modify TaskDetails.ascx to conform to BMS UI standards
> ----------------------------------------------------------------------
> --
>
> D:\projects\BMS_prj_tasks\source\Oasis.BMS\Oasis.BMS.UI\Task>svn log
> -r1089 -v UserControls\TaskDetails.ascx
> ----------------------------------------------------------------------
> --
>
> As you can see, the UserControls\TaskDetails.ascx file has no
> knowledge
> of this revision.
>
> Now if I list the last 5 revisions for the UserControls
> \TaskDetails.ascx
> file, I get:
>
>
> D:\projects\BMS_prj_tasks\source\Oasis.BMS\Oasis.BMS.UI\Task>svn log
> --limit 5 UserControls\TaskDetails.ascx
> ----------------------------------------------------------------------
> --
> r996 | PIsmail | 2006-11-24 19:31:31 +1100 (Fri, 24 Nov 2006) | 1 line
>
>
> ----------------------------------------------------------------------
> --
> r977 | PIsmail | 2006-11-23 18:20:11 +1100 (Thu, 23 Nov 2006) | 4
> lines
>
> Several fixes include:
> CreateTask.aspx appearance fix
> CreateTask.aspx Refresh/Back causing recreation now prevented
> Ensure Task Notes for non workflow tasks (ie no status drop) doesn't
> cause crash
> ----------------------------------------------------------------------
> --
> r893 | AClark | 2006-11-20 16:36:50 +1100 (Mon, 20 Nov 2006) | 5 lines
>
> - Altered TaskManager.EscalateTask() to return the modified TaskObj
> - Altered placement of btnEscalate on TaskDetails.ascx
> - Repaired Task Status/SLA date handling on TaskDetails.ascx.cs
> - Altered Escalation process to add auto note and close Task Details.
>
> ----------------------------------------------------------------------
> --
> r803 | PIsmail | 2006-11-10 17:41:06 +1100 (Fri, 10 Nov 2006) | 1 line
>
>
> ----------------------------------------------------------------------
> --
> r794 | PIsmail | 2006-11-09 18:36:16 +1100 (Thu, 09 Nov 2006) | 5
> lines
>
> Fixed/Enhanced items associated with:
> CreateTask.aspx
> TaskClassification.aspx
> taskDetails.ascx
> WorkItemNotes.ascx
> ----------------------------------------------------------------------
> --
I notice you're running the log command from a working copy. I'll bet
the working copy is not up to date. Run "svn update" (or the
TortoiseSVN equivalent) and then get the log again. You should get
everything now.
When used against a working copy, "svn log" only shows you the log up
to the state of your working copy; if your working copy is not up to
date, you don't get an up-to-date log either.
You can also say "svn log url://to/repository" to always get an up-to-
date log.
--
To reply to the mailing list, use your mailer's Reply To All function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 30 14:02:38 2006