What am I doing wrong here? svn propedit svn:ignore log I set it to ''*'' So that svn propget svn:ignore log returns *. So, I should be ignoring all log files, right? So how come a svn status shows my modified logs?
On 7/6/05, Joe Van Dyk <joevandyk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> What am I doing wrong here? > > svn propedit svn:ignore log > > I set it to ''*'' > > So that svn propget svn:ignore log returns *. > > So, I should be ignoring all log files, right? > > So how come a svn status shows my modified logs?Joe- You need to remove the logs from your Subversion repository, too. SVN won''t ignore files that have already been explicitly added to the repository. Cheers, Ben
Ben Schumacher <benschumacher@...> writes:> > On 7/6/05, Joe Van Dyk <joevandyk@...> wrote: > > What am I doing wrong here? > > > > svn propedit svn:ignore log > > > > I set it to ''*'' > > > > So that svn propget svn:ignore log returns *. > > > > So, I should be ignoring all log files, right? > > > > So how come a svn status shows my modified logs? > > Joe- > > You need to remove the logs from your Subversion repository, too. SVN > won''t ignore files that have already been explicitly added to the > repository. > > Cheers, > > Ben >So does the process go ignore->remove, or remove->ignore? Being a version control newbie, I''m struggling with the same issues. While we''re at it another question. From the docs I have read, Subversion seems to be directory-based in how it records revisions. IOW, if I checkout say list.rhtml from an svn repo, make changes, and commit, all elements at the same level get their revision number incremented in addition to the list.rhtml file, regardless if they have changed or not since their last commit. Doesn''t that make fine-grained control of individual file revisions difficult? Thanks in advance for any input.
dave davidson said the following on 2005-07-06 15:00:> So does the process go ignore->remove, or remove->ignore? Being a version > control newbie, I''m struggling with the same issues.Doesn''t matter. You should be committing these changes in the same transaction anyway. Bye, François
On 7/6/05, dave davidson <datapanix-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Ben Schumacher <benschumacher@...> writes: > > > > > On 7/6/05, Joe Van Dyk <joevandyk@...> wrote: > > > What am I doing wrong here? > > > > > > svn propedit svn:ignore log > > > > > > I set it to ''*'' > > > > > > So that svn propget svn:ignore log returns *. > > > > > > So, I should be ignoring all log files, right? > > > > > > So how come a svn status shows my modified logs? > > > > Joe- > > > > You need to remove the logs from your Subversion repository, too. SVN > > won''t ignore files that have already been explicitly added to the > > repository. > > > > Cheers, > > > > Ben > > > > So does the process go ignore->remove, or remove->ignore? Being a version > control newbie, I''m struggling with the same issues. > > While we''re at it another question. From the docs I have read, Subversion > seems to be directory-based in how it records revisions. IOW, if I checkout > say list.rhtml from an svn repo, make changes, and commit, all elements at the > same level get their revision number incremented in addition to the list.rhtml > file, regardless if they have changed or not since their last commit. Doesn''t > that make fine-grained control of individual file revisions difficult?Actually, it''s repository-based. Every commit you make is remembered by a global repository version number. So, every time you make a commit, all the files get their version number incremented. So, there aren''t individual file revisions. Which actually makes life a lot easier. And you can always go back in time to see the history of the entire repository or of an individual file.
On 7/6/05, dave davidson <datapanix-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> While we''re at it another question. From the docs I have read, Subversion > seems to be directory-based in how it records revisions. IOW, if I checkout > say list.rhtml from an svn repo, make changes, and commit, all elements at the > same level get their revision number incremented in addition to the list.rhtml > file, regardless if they have changed or not since their last commit. Doesn''t > that make fine-grained control of individual file revisions difficult?That''s not correct. First, you can very easily check in a single file or multiple directories for that matter. Subversion is actually "repository-based" for "revisions". It actually doesn''t try to make some hierachy of file revisions within the repository - it simply keeps a single revision number and moves along. There is no loss of granularity at all with their methodology. You can pick and choose to pull out any file or directory from any revision and combine as you please. Also, the repository does store the metadata for a revision for individual files. You can get information on which files changed at which revision as well as which revisions affected particular files very easily. It''s simply a matter of revision number being used differently then commonly thought of. You get use to it very quickly and life gets much much easier :) -- John W Higgins wishdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org