[
https://issues.apache.org/jira/browse/SVN-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Foad updated SVN-3653:
-----------------------------
Component/s: (was: src)
> svn update should not output svn:external fetches if they have not been
> updated
> -------------------------------------------------------------------------------
>
> Key: SVN-3653
> URL: https://issues.apache.org/jira/browse/SVN-3653
> Project: Subversion
> Issue Type: Improvement
> Affects Versions: 1.6.x
> Reporter: Subversion Importer
> Priority: Major
> Fix For: unscheduled
>
> Attachments: 1_notify.c.patch, 2_notify.c.patch.2
>
>
> {noformat:nopanel=true}
> Normally, when doing svn update on an already up to date working copy, the
> only
> output is:
> At revision X
> However, if there are svn:externals references in the working copy, the same
> command always echoes:
> Fetching external item into path/to/item
> External at revision X.
> At revision X
> IMHO, if the external item was not changed, nothing should be echoed.
> ----------
> PD: relevant IRC conversation:
> (15:36:28) paseante: when using svn:externals, is there any way to prevent
> messages like this one:
> (15:36:28) paseante: Fetching external item into
> (15:36:28) paseante: External at revision 47399.
> (15:36:28) paseante: From appearing?
> (15:37:22) paseante: it appears every time you svn upgrade
> (15:37:35) paseante: even if it is up to date
> (15:53:02) stsp: there's no way to avoid it, sorry
> (15:53:29) stsp: there's been a request to suppress the message before
> (15:53:50) stsp: there's no technical problem with not printing the message
> (15:54:05) stsp: but someone has to write a patch :)
> (15:54:29) stsp: (to suppress the message if the external didn't receive any
> updates)
> (15:59:02) paseante: is there an issue in the tracker for this?
> (16:07:33) stsp: paseante, i'll check
> (16:27:42) stsp: paseante, no I don't think there's an issue -- can you file
> one? thanks
> {noformat}
> Original issue reported by *kovan*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
