svn commit: r1932906 - subversion/trunk/subversion/svnbrowse

[email protected]
Newsgroups gmane.comp.version-control.subversion.svn
Message-ID <177566079121.716982.15625647260757545472@svn03-he-fi>
Author: rinrab
Date: Wed Apr  8 15:06:30 2026
New Revision: 1932906

Log:
Follow-up to r1932903: Fix spelling mistakes in a comment.

* subversion/svnbrowse/model.c
  (svn_browse__model_create): Typofixes.

Modified:
   subversion/trunk/subversion/svnbrowse/model.c

Modified: subversion/trunk/subversion/svnbrowse/model.c
==============================================================================
--- subversion/trunk/subversion/svnbrowse/model.c	Wed Apr  8 14:55:12 2026	(r1932905)
+++ subversion/trunk/subversion/svnbrowse/model.c	Wed Apr  8 15:06:30 2026	(r1932906)
@@ -161,7 +161,7 @@ svn_browse__model_create(svn_browse__mod
   model->client = ctx;
   model->session = session;
 
-  /* If the revision is ovbiously HEAD, we are not going to use the resolved
+  /* If the revision is obviously HEAD, we are not going to use the resolved
    * revnum, but rely on svn_ra_get_dir2() doing that for us. It allows the
    * browser to always browse on the latest revision and catch-up recent
    * commits as session is active.
@@ -172,9 +172,9 @@ svn_browse__model_create(svn_browse__mod
    * would be too complicated and rather confusing. That's why we will fallback
    * to what the client is doing instead of reinventing the wheel.
    *
-   * When invoked from a working copy, it's not HEAD either. It's should point
-   * to WORKING, i.e. revnum should not change. Again rescanning the working
-   * copy is possible but we assume it never changes.
+   * When invoked from a working copy, it's not HEAD either. It should point to
+   * WORKING, i.e. revnum should not change. Again rescanning the working copy
+   * is possible but we assume it never changes.
    */
 
   if (peg_rev.kind == svn_opt_revision_head &&
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.