From: Shawn Pearce <spearce@spearce.org>
To: Junio Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH 0/5] More ref logging
Date: Fri, 19 May 2006 05:14:56 -0400 [thread overview]
Message-ID: <20060519091456.GH22257@spearce.org> (raw)
These are on top of the other five I just sent:
* [PATCH 1/5] Correct force_write bug in refs.c
Yea there was a bug in the last bug fix. Now we
really don't write the ref unless we need to.
* [PATCH 2/5] Change order of -m option to update-ref.
Minor documentation nit noticed by Junio.
* [PATCH 3/5] Include ref log detail in commit, reset, etc.
Enhance some core tools to use the new '-m' switch with
update-ref. Trivial but requires the new update-ref.
* [PATCH 4/5] Create/delete branch ref logs.
This was discussed on #git earlier this morning.
Automatically create the ref log if -l is given when creating
a branch and delete the log when deleting the branch.
* [PATCH 5/5] Enable ref log creation in git checkout -b.
Fix git checkout -b to behave like git branch.
--
Shawn.
next reply other threads:[~2006-05-19 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 9:14 Shawn Pearce [this message]
[not found] ` <20060519071603.11d3be5d.seanlkml@sympatico.ca>
2006-05-19 11:16 ` [PATCH 0/5] More ref logging Sean
2006-05-21 0:50 ` Shawn Pearce
[not found] ` <20060520224344.7ebca48b.seanlkml@sympatico.ca>
2006-05-21 2:43 ` Sean
2006-05-21 4:51 ` Shawn Pearce
[not found] ` <20060521010944.78903774.seanlkml@sympatico.ca>
2006-05-21 5:09 ` Sean
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=20060519091456.GH22257@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).