git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Mike Hommey <mh@glandium.org>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: confused about preserved permissions
Date: Mon, 20 Aug 2007 22:10:42 +0200	[thread overview]
Message-ID: <20070820201042.GA9942@glandium.org> (raw)
In-Reply-To: <20070820200719.GE5544@steel.home>

On Mon, Aug 20, 2007 at 10:07:19PM +0200, Alex Riesen <raa.lkml@gmail.com> wrote:
> Mike Hommey, Mon, Aug 20, 2007 21:50:37 +0200:
> > On Mon, Aug 20, 2007 at 09:43:28PM +0200, Jan Hudec <bulb@ucw.cz> 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.)

Mike

  reply	other threads:[~2007-08-20 20:11 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 16:44 confused about preserved permissions martin f krafft
2007-08-20 16:54 ` Pierre Habouzit
2007-08-20 17:38   ` martin f krafft
2007-08-20 17:41 ` Mike Hommey
2007-08-20 17:58   ` David Kastrup
2007-08-20 18:13     ` Mike Hommey
2007-08-20 18:44       ` David Kastrup
     [not found]       ` <86zm0mgicy.fsf@lola.quinscape.zz>
2007-08-20 18:48         ` Mike Hommey
2007-08-20 19:43           ` Jan Hudec
2007-08-20 19:50             ` Mike Hommey
2007-08-20 20:07               ` Alex Riesen
2007-08-20 20:10                 ` Mike Hommey [this message]
2007-08-20 20:27                   ` Jan Hudec
2007-08-20 20:42                   ` David Kastrup
2007-08-20 20:44                     ` Mike Hommey
2007-08-20 20:08               ` Jan Hudec
2007-08-20 20:39           ` David Kastrup
2007-08-20 20:50             ` Mike Hommey
2007-08-20 21:03               ` David Kastrup
2007-08-21  1:35               ` Shawn O. Pearce
2007-08-21  2:06                 ` Junio C Hamano
2007-08-21  5:34                   ` Mike Hommey
2007-08-21  6:04                     ` David Kastrup
2007-08-21 18:01   ` René Scharfe
2007-08-21 18:01   ` [PATCH] Documentation: update tar.umask default René Scharfe
2007-08-21 21:15     ` Mike Hommey
2007-08-22 21:03       ` René Scharfe
2007-08-20 18:35 ` confused about preserved permissions Alex Riesen
2007-08-22 12:18 ` Benoit SIGOURE
2007-08-22 12:52   ` Johannes Sixt
2007-08-22 22:09   ` Junio C Hamano
2007-08-23  6:00     ` martin f krafft
2007-08-23  6:12       ` David Kastrup
2007-08-23  6:23         ` martin f krafft
2007-08-23  7:48         ` Benoit SIGOURE
2007-08-23  7:57           ` Junio C Hamano
2007-08-23  8:08             ` David Kastrup
2007-09-03 18:59           ` Jan Hudec
2007-08-23  7:03       ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070820201042.GA9942@glandium.org \
    --to=mh@glandium.org \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).