From: Bill Lear <rael@zopyra.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: Git log of all (modifying) commands run on a repo?
Date: Wed, 7 Feb 2007 17:00:26 -0600 [thread overview]
Message-ID: <17866.23050.937572.192253@lisa.zopyra.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702071441160.8424@woody.linux-foundation.org>
On Wednesday, February 7, 2007 at 14:49:50 (-0800) Linus Torvalds writes:
>...
>The "reflog" is kind of that, and you can literally do
>
> less .git/logs/refs/heads/master
>
>to get some kind of idea what's up.
>
>Newer gits enable reflogs by default, older gits don't (and *really* old
>git versions don't support it at all).
Ah, I don't seem to have .git/logs at all.
We plan to upgrade to 1.5 when it's out, so I guess we'll just
have to wait.
Bill
next prev parent reply other threads:[~2007-02-07 23:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 22:15 Git log of all (modifying) commands run on a repo? Bill Lear
2007-02-07 22:29 ` Jakub Narebski
2007-02-07 22:39 ` Bill Lear
2007-02-07 22:59 ` Jakub Narebski
2007-02-07 22:49 ` Linus Torvalds
2007-02-07 22:56 ` Junio C Hamano
2007-02-07 23:03 ` Shawn O. Pearce
2007-02-07 23:26 ` Linus Torvalds
2007-02-07 23:36 ` Junio C Hamano
2007-02-07 23:46 ` Linus Torvalds
2007-02-07 23:53 ` Jakub Narebski
2007-02-07 23:59 ` Johannes Schindelin
2007-02-08 0:05 ` Shawn O. Pearce
2007-02-08 0:26 ` Junio C Hamano
2007-02-08 0:41 ` Johannes Schindelin
2007-02-08 0:50 ` Junio C Hamano
2007-02-08 0:56 ` Johannes Schindelin
2007-02-08 17:51 ` Linus Torvalds
2007-02-08 18:36 ` Johannes Schindelin
2007-02-07 22:57 ` Shawn O. Pearce
2007-02-07 23:00 ` Bill Lear [this message]
2007-02-07 23:29 ` Linus Torvalds
2007-02-07 23:31 ` Bill Lear
2007-02-07 23:02 ` Linus Torvalds
2007-02-08 8:26 ` Johannes Sixt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17866.23050.937572.192253@lisa.zopyra.com \
--to=rael@zopyra.com \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.
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 NNTP newsgroup(s).