On 12/1/2010 6:40 AM, Ludwig, Michael wrote:
>
>> And if you did have the name lookup you want, you still have to
>> deal with the issue that in every rev where the name is found it
>> may be some different object.
>
> It is not an issue, Andrey and I mentioned that repeatedly.
I think the functionality he wants is different.
> The revision disambiguates the name and provides identity.
It seems like you are asking for what you would get if you collate the
output of:
svn ls -r? URL
where you cycle the ? through all the revisions.
That is, you want every instance where the name appears regardless of
the objects referenced by that name.
I think Andrey wants something more like:
svn log -r0:? URL_at_PEG
where the ? is the highest rev where the same object was present at
that path. Or at least to find the value of that highest rev.
But for me, the question I would want to be able to answer would more
likely be "where else was this copied?" as in "what release tags include
this file or its descendants?" or "what is its new name after a move in
a future rev?"
But we all agree that there are things you might want that you can't do
easily. The developers here all use an issue tracking system with
tickets to discuss the changes being done and always include the ticket
number in a certain format in the commit message for every commit - in
fact we just added a pre-commit hook to enforce that. And I think the
svn revision that completes/closes an issue goes back to the ticket.
This doesn't exactly address tracking changes to individual files and
objects, but at a higher level it connects the purpose of a change with
the work itself and lets you use a better tool to handle the related
context, making it less likely that you would need a brute-force search
for lost items.
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2010-12-01 17:30:03 CET