Re: git log --follow for directories

[Laszlo Papp]

Junio C Hamano gitster at pobox.com writes:

 
 Laszlo Papp lpapp at kde.org writes:
 
  Is there any benefit about having it like it is today or is it just
  the usual no one has implemented it yet?
 
 It actually is even more sketchy than that.  A single file following
 was done merely as a checkbox item that works majority of the time,
 and any mergy history that renames the file on one side of the side
 branch but not on the other may not truly follow it.
 

Well, in worst case, why not have something like --follow-dirs, then?

The case at hand is that we unfortunately named a directory based on the
codename of some software for the time.

Now, we have improved that software and the codename is different
accordingly. Now, instead of pastcodename, I would change the directory
name to src to be future proof, but here, I face these difficulties:

1) The directory name is stuck with some ancient codename and it therefore
will be confusing for the rest of the life cycle for this project.

2) We get unfollowable directories. At best, we could use some scripts to
work this around, but why not address this directly in git?

I think renaming a directory without losing the history would be really cool
to have, one way or another. If that requires a separate option, I am happy
with that, but what I would really like to avoid is not being able to rename
directories without losing the history.

Note that I am speaking from user point of view. I do not know the
nitty-gritty technical details, but that is just implementation details as
far as I am concerned, anyway.

--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

git log --follow for directories

[Laszlo Papp]

Hi,

I have just realized that this would not work on directories
triggering directory renames somewhat pointless for those who want to
keep track of a group of files in directories.

It is unfortunate when you have a directory with many files and more
often than not, you would like to look at the history of all rather
than individually.

Is there any benefit about having it like it is today or is it just
the usual no one has implemented it yet?

Cheers, L.

PS.: I will not stand up for implement this though, but of course I
will be very grateful if someone else decides to do so.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html