-----BEGIN PGP SIGNED MESSAGE-----
Hyrum K. Wright wrote:
> On Nov 12, 2009, at 5:53 AM, Julian Foad wrote:
>> Stefan Sperling wrote:
>>> On Thu, Nov 12, 2009 at 11:01:10AM +0000, Julian Foad wrote:
>>>> We try hard not to change the output format. Why do we need to change it
>>>> here? The other subcommands manage to convert abs paths back to rel
>>>> paths for display.
>>> How? Can you show an example?
>> I'm sure I recall somebody mentioning on dev@ that they did this for at
>> least one other command earlier this year.
>> A search for "to_rel" finds info_receiver_relpath_wrapper() which is
>> undocumented, aargh, but looks like it does that sort of thing.
>> Basically you just have to know what your base path is, transfer it
>> (through a baton if necessary) to the output function, and strip it off
>> the received abspath (making sure the base path is in canonical absolute
>> form as well).
If we're to use info_receiver_relpath_wrapper() and a baton to pass the
relative path and other info, won't it resemble the implementation(for
backward compatibility)which is at present?
> FWIW, centralization and sanitization of relative path output in an absolute path world is issue 3464:
Thank you Hyrum, in that case implementing using a separate wrapper(now)
for info alone becomes obsolete right?
Thanks & Regards,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
Received on 2009-11-12 15:33:02 CET