On Mon, Aug 20, 2007 at 10:42:34PM +0200, David Kastrup <dak@xxxxxxx> wrote: > Mike Hommey <mh@xxxxxxxxxxxx> writes: > > > On Mon, Aug 20, 2007 at 10:07:19PM +0200, Alex Riesen <raa.lkml@xxxxxxxxx> wrote: > >> Mike Hommey, Mon, Aug 20, 2007 21:50:37 +0200: > >> > On Mon, Aug 20, 2007 at 09:43:28PM +0200, Jan Hudec <bulb@xxxxxx> wrote: > >> > > Git does not have tracking of file's history either. > >> > > >> > Well, it has ways to track file's history, with blame and log, for > >> > example. There is nothing similar for directories, though it could be > >> > possible to do. > >> > >> It would be not exactly "tracking". You can present the history of > >> changes which involved the said directory. > >> > >> And you could do it from day one: git log -- sub/dir > > > > It could be possible to really do tracking, too, like it is possible for > > files (including renames, moves, etc.) > > You are confused. Git does not track renames or moves for files, > either. It just records snapshots. It reverse engineers renames, > moves, copying when cranking out diffs and logs and blames. Yes, I know. And that could be done for directories, too. Mike - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
