On Wed, Mar 29, 2006 at 03:21:17PM -0500, George Georgalis wrote:
> On Wed, Mar 29, 2006 at 12:07:49PM -0800, Lan Barnes wrote:
> >On Wed, Mar 29, 2006 at 02:44:23PM -0500, George Georgalis wrote:
> >> So I'm giving subversion a try... Something that is
> >> not mentioned in the doc, at least I cannot find,
> >> in my cvs repo, these lines are in my CVSROOT/config
> >>
> >> LocalKeyword=GeorgalisG=CVSHeader
> >> KeywordExpand=iGeorgalisG,Log
> >>
> >> so, whenever I put the string "$GeorgalisG$" in a repo file, it
> >> gets expanded to
> >>
> >> # $GeorgalisG: mkinst/qmail-inst.sh,v 1.26 2006/02/20 19:32:09 geo Exp $
> >>
> >> when that file is committed. nice handy information on who committed
> >> to which repo, with path to file and date.
> >>
> >> I see this:
> >> http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.special.keywords
> >> but there is no mention of anything as easy as configuring
> >> for $RepoName$ for that result... is that supported in svn?
> >>
> >
> >According to the Nagel book, svn supports 5 keywords but you have to
> >turn it on by adding a space-delimited list of them to the property
> >svn:keywords. This is from pp 92-93. The book is available in pdf for
> >download from http://www.phptr.com/perens. Amazon has a paper copy. It's
> >a good book.
>
> It doesn't look like svn has the mustard to do the task.
>
> it may seem odd, but I think it would be valuable to embed the
> repo, path, revision, commit date and commiter to one line of a
> file. The real value is when file gets emailed or something, svn
> info is not available. I don't want the URI, because that could
> change depending on how it was checked out. And if a user has to
> enter all those keywords on separate lines, that's asking for out
> of spec files.
>
> $CompanyInc$ expanding to on the line has worked very nicely for
> me.
>
> >I personally would almost rather put bugs in code than keywords, because
> >they confuse and confound diffs. The information is all available
> >elsewhere, and clean diffs make an SCMer's job so much easier.
>
> actually they (the keyword I presented), works very well with
> diff. if it's two checked out revisions you can figure out which
> +/- lines correspond to which version--looking at the header
> diff. if it's a modified checked out revision then the header is
> unchanged and not in the diff.
>
> >There is no accounting for taste ...
>
> *sigh* if I could program it in a config at least...
Check out svn resources and triggers before giving up. Resources allow
you to attach key-value pairs at two levels, and triggers obviously
would allow emailing them on events.
I've been round and round on keywords. Developers like them ("Oooo,
shiny!"), SCMers don't. Be happy with who you are, I guess.
CVS is a tired old dog. Getting away from it is a Good Thing.
--
Lan Barnes [EMAIL PROTECTED]
Linux Guy, SCM Specialist 858-354-0616
Tcl/Tk Enthusiast
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
