From: Shawn Pearce <spearce@spearce.org>
To: git@vger.kernel.org
Subject: [RFC 0/5] Log history of a ref
Date: Wed, 17 May 2006 05:54:17 -0400 [thread overview]
Message-ID: <20060517095417.GA28529@spearce.org> (raw)
The following 5 [RFC] patches from me are all related to logging
changes made to a ref. These patches contain the same basic idea
as the two patches I floated earlier this week. Log files reside
in .git/logs<ref> and logging is enabled either by creating the
log file or by setting 'core.logAllRefUpdates' to true.
Summary is:
* [RFC 1/5] Remove unnecessary local in get_ref_sha1.
A minor code cleanup.
* [RFC 2/5] Improve abstraction of ref lock/write.
A major reorg of the write_ref_sha1 APIs. This reorg allows
all internal code to use the same logic for updating any ref,
which makes it much easier to hook logging in.
* [RFC 3/5] Convert update-ref to use ref_lock API.
Modify update-ref to use the reorg'd write_ref_sha1 API.
* [RFC 4/5] Log ref updates to logs/refs/<ref>
Add logging of refs. This is the pretty much my latest
logging patch but cleaned up and built on the above.
* [RFC 5/5] Support 'master@2 hours ago' syntax
Extend the SHA1 syntax to search the log for the SHA1 which
was valid at the given point in time.
I still need to fix the receive-pack code to log ref changes prior
to running the update hook. I'll probably look at that later this
week. I also need to edit the ~20 sites which call 'git-update-ref'
to make use of the new "-m <reason>" flag.
--
Shawn.
reply other threads:[~2006-05-17 9:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060517095417.GA28529@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.