Feature Request: svn ls --no-ignore-externals

["John E. Bossom" <Jo...@ca.ibm.com>]

The list subcommand is excellent for writing scripts over the set of files/directories as listed in the repository, without having to fetch the source. I have been experimenting with using svn:externals leveraging the '^' syntax for describing logical views of my repository. (I discovered that if you are careful, a single commit will handle all the externals if they are from the same repository). However, I discovered that the svn list subcommand has no option for walking the externals. I think this would be a really useful feature - to be able to list what would be checked out or exported without having to actually do it. 
Introducing an option such as --no-ignore-externals would allow the default for svn list to remain the same, but still allow the option to walk the externals.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2385612

Re: Feature Request: svn ls --no-ignore-externals

[Julian Foad <ju...@wandisco.com>]

John E. Bossom wrote:
> The list subcommand is excellent for writing scripts over the set of
> files/directories as listed in the repository, without having to fetch
> the source. I have been experimenting with using svn:externals
> leveraging the '^' syntax for describing logical views of my
> repository. (I discovered that if you are careful, a single commit
> will handle all the externals if they are from the same repository).
> However, I discovered that the svn list subcommand has no option for
> walking the externals. I think this would be a really useful feature -
> to be able to list what would be checked out or exported without
> having to actually do it.
>  
> Introducing an option such as --no-ignore-externals would allow the
> default for svn list to remain the same, but still allow the option to
> walk the externals.

That sounds like a logical enhancement that falls totally within the
scope of the existing expectations, so I think we would gladly accept
it.

It's possible that somebody will see this and write a patch to implement
it, but, from experience, I would say it's unlikely. Might you or a
colleage be able to work on it? If you would like some help on how to
get started, please just ask or see
<http://subversion.tigris.org/development.html>.

- Julian

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2385629