Re: SVN keyword replacement

On 2019-02-19 20:37:01 +, Scott Bloom wrote: > Thanks.. That is exactly what Im looking for! Even if this is implemented, there's an issue with all these keywords with path/URL information in them: the expanded path is the one of the revision that last changed the file, not the current one! Fo

Re: SVN keyword replacement

Mark Phippard wrote on Tue, 19 Feb 2019 20:53 +00:00: > It ought to cover everything. If this looks like it is going to take a > considerable amount of your time then you might want to post what you > plan to do on the dev@ mailing list. There is no point spending time on > this if someone plans

Re: SVN keyword replacement

On Tue, Feb 19, 2019 at 3:37 PM Scott Bloom wrote: > Thanks.. That is exactly what Im looking for! > > > > Ill contact you off list on contribution procedures if that’s ok. > More info then you could ever hope for is available here: https://subversion.apache.org/docs/community-guide/ It ought

RE: SVN keyword replacement

Thanks.. That is exactly what Im looking for! Ill contact you off list on contribution procedures if that’s ok. Scott From: Mark Phippard Sent: Tuesday, February 19, 2019 10:30 To: Scott Bloom Cc: Pavel Lyalyakin ; users@subversion.apache.org Subject: Re: SVN keyword replacement On Tue, Feb

Re: SVN keyword replacement

On Tue, Feb 19, 2019 at 2:09 PM Daniel Shahaf wrote: > Mark Phippard wrote on Tue, 19 Feb 2019 18:30 +00:00: > > One idea that occurred to me would be adding a new value of %W that is > > similar to %P except the path is relative to the root of the working > > copy. Assuming that is generally the

Re: SVN keyword replacement

Mark Phippard wrote on Tue, 19 Feb 2019 18:30 +00:00: > One idea that occurred to me would be adding a new value of %W that is > similar to %P except the path is relative to the root of the working > copy. Assuming that is generally the root of your project, such as > /trunk this would give the

Re: SVN keyword replacement

On Tue, Feb 19, 2019 at 1:13 PM Mark Phippard wrote: > On Tue, Feb 19, 2019 at 1:08 PM Scott Bloom wrote: > >> Unfortunately %P still includes branch directories…. >> >> >> >> > Yes, it is repository relative. That is the best you are going to get out > of Subvers

RE: SVN keyword replacement

attributes? Scott From: Mark Phippard Sent: Tuesday, February 19, 2019 10:13 To: Scott Bloom Cc: Pavel Lyalyakin ; users@subversion.apache.org Subject: Re: SVN keyword replacement On Tue, Feb 19, 2019 at 1:08 PM Scott Bloom mailto:sc...@towel42.com>> wrote: Unfortunately %P still includes

Re: SVN keyword replacement

On Tue, Feb 19, 2019 at 1:08 PM Scott Bloom wrote: > Unfortunately %P still includes branch directories…. > > > > Yes, it is repository relative. That is the best you are going to get out of Subversion. Subversion does not really have branches or tags. It has pat

RE: SVN keyword replacement

Unfortunately %P still includes branch directories…. Scott From: Scott Bloom Sent: Tuesday, February 19, 2019 10:05 To: Scott Bloom ; Mark Phippard ; Pavel Lyalyakin Cc: users@subversion.apache.org Subject: RE: SVN keyword replacement Just a note.. the latest PDF/Web pages for SVN don’t

RE: SVN keyword replacement

Just a note.. the latest PDF/Web pages for SVN don’t have this information. Scott From: Scott Bloom Sent: Tuesday, February 19, 2019 10:04 To: Mark Phippard ; Pavel Lyalyakin Cc: users@subversion.apache.org Subject: RE: SVN keyword replacement Mark, This looks like its exactly what Im

RE: SVN keyword replacement

Mark, This looks like its exactly what Im looking for! Thanks Scott From: Mark Phippard Sent: Tuesday, February 19, 2019 10:01 To: Pavel Lyalyakin Cc: Scott Bloom ; users@subversion.apache.org Subject: Re: SVN keyword replacement On Tue, Feb 19, 2019 at 12:55 PM Pavel Lyalyakin

RE: SVN keyword replacement

ject: Re: SVN keyword replacement Hello Scott, On Tue, Feb 19, 2019 at 8:41 PM Scott Bloom wrote: > > Our repository currently uses $HeadURL, and it works as advertised. > > However, I would prefer just the file from ^, this way if there is a branch, > and a switch, everyfile wont

Re: SVN keyword replacement

On Tue, Feb 19, 2019 at 12:55 PM Pavel Lyalyakin < pavel.lyalya...@visualsvn.com> wrote: > Hello Scott, > > On Tue, Feb 19, 2019 at 8:41 PM Scott Bloom wrote: > > > > Our repository currently uses $HeadURL, and it works as advertised. > > > > However, I would prefer just the file from ^, this way

Re: SVN keyword replacement

Hello Scott, On Tue, Feb 19, 2019 at 8:41 PM Scott Bloom wrote: > > Our repository currently uses $HeadURL, and it works as advertised. > > However, I would prefer just the file from ^, this way if there is a branch, > and a switch, everyfile wont have to be rebuilt. > > The redbooks lists nothi