Jay McCarthy <firstname.lastname@example.org> writes:
> Hi, I've been following the mailing list for a while and reading all the
> docs and source and I was wondering about something...
> The first entry in the General Problems secton of notes/STACK
> states that:
> "updates (right now) don't bump the revision of every entry as they
> should; instead we're only bumping the changed entries."
Oh my, I'm so sorry to have wasted your time. That STACK file is
nearly a year old. I doubt that anything in there is relevant or true
anymore! We should delete the file completely.
> If that is correct (I have not looked at the code which gets the values
> for the keywords prior to their substitution), then will there be a way
> to get the last date and revision a file was changed? And should there
> be? I know that the subversion developers think that CVS was incorrect
> in versioning each file separately, and this type of thing would be a
> regression (if it were implemented by keeping track of that information
> in the repository.)
Just run 'svn st -v' (--verbose). Try 'svn help status' to understand
the output. It shows you the last revision in which a file changed,
and by whom. If you need to know the date of the revision, try 'svn
log -r N'.
> When trying to think of a way to remedy this, this was my line of
> When a 'svn update' is issued, update all file's rev number and only
> change the keywords on files that have changed.
That's in fact what we already do.
> However, thinking about this you have the problem where a checkout won't
> know which files have changed unless that's stored in the repository.
> When the file is in the repository is the keyword expansion directive
> stored ($Keyword: $)
yes... keywords are always contracted in the repository.
> Is any of this thought correct? Talked about before?
> Am I an idiot? I don't know... perhaps someone can correct me.
Sorry, I'm not understanding your mail. What's your question? What's
the problem you're trying to solve?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Oct 21 14:37:10 2006