[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Feature requests for post 1.0

From: <kfogel_at_collab.net>
Date: 2003-11-26 18:11:57 CET

David Waite <mass@akuma.org> writes:
> Perhaps a compromise would be to perform this history tag expansion
> only on export?

We're getting into real edge-case territory here, and the ratio

               benefit
           ------------------
           maintenance burden

diminishes. I'm not going to say -1, since there's no concrete
proposal yet, but -0.9 on the general idea :-).

Subversion generally separates historical metadata and file contents.
To start blending them is to create a different kind of system, and we
haven't even begun to think about the design implications of that.

-Karl

> On Nov 26, 2003, at 9:59 AM, Greg Hudson wrote:
>
> > On Wed, 2003-11-26 at 07:54, nick vajberg wrote:
> >> 1) New svn:keyword : History. This would replace
> >> $History$ with a verbose, nicely formatted history of
> >> the file. We have to distribute source files gzip'ed
> >> and the recipient require history comments in each
> >> file header. Updating the history manually is very
> >> time consuming and errorphrone. Any thoughts?
> >
> > I'll assume you want this to behave like an actual keyword, not like
> > the
> > $Log$ pseudo-keyword in RCS/CVS (where history information is added
> > incrementally after the $Log$ keyword, certain operations can mess up
> > the history, and there's no way to prevent merge conflicts resulting
> > from the history).
> >
> > Our translation code assumes that keywords are short and can't span
> > multiple lines. That could change, but if the keyword text which needs
> > to be substituted can be very long ("$History: <100Kbytes here>"), then
> > substitution can't be done streamily. If you read "$History:" followed
> > by a million bytes, and the end of the file comes before the closing
> > '$', then you didn't really have a keyword, so you have to put those
> > million bytes back in untouched, so you'd better have been saving them.
> > Not the end of the world, maybe, but it's another reason why it's a
> > pain
> > in the ass.
> >
> > If dollar signs appear in the log, they'd have to be quoted, which kind
> > of interferes with the "nicely formatted" part.
> >
> > Fetching the log information for a file during translation is would
> > require opening an extra repository session for that purpose. Doable,
> > but also a pain in the ass, and it isn't 100% transparent to the user
> > (for instance, if you use svn+ssh and ssh requires a password, opening
> > an extra session means being asked for your password an extra time).
> >
> > So, nobody here is likely to devote time to it, and even if someone
> > wrote a patch, we'd be very leary of committing it.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: dev-help@subversion.tigris.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 26 18:57:23 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.