From: Shawn Pearce <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 5/5] Enable ref log creation in git checkout -b.
Date: Tue, 23 May 2006 23:52:34 -0400 [thread overview]
Message-ID: <20060524035234.GA13329@spearce.org> (raw)
In-Reply-To: <7vk68fyarn.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> I've swallowed all 10 and pushed them out in "pu", but could you
> add tests to check the Porcelainish commands you touched with
> this series to make sure they all log correctly?
Sure. I've been putting it off as I've been busy the past few days
and have also been thinking about trying to rebuild reflog using a
tag/annotation branch style, which might be more generally useful
to others. So I've been debating about whether or not I should
ask you to pop reflog out of pu indefinately.
> BTW, I noticed that a patch earlier in the series depended on
> something not in "master" (it's rfc2822_date from js/fmt-patch
> series). Generally I do not want to make a branch hostage of
> another branch by introducing a dependency, but for now I'll
> pull in early part of js/fmt-patch branch into sp/reflog branch
> and see what happens.
Doh. Sorry about that one. I saw it in date.c and used it, not
realizing it was only in pu.
--
Shawn.
next prev parent reply other threads:[~2006-05-24 3:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 9:17 [PATCH 5/5] Enable ref log creation in git checkout -b Shawn Pearce
2006-05-21 9:42 ` Junio C Hamano
2006-05-24 3:52 ` Shawn Pearce [this message]
2006-05-24 4:32 ` Junio C Hamano
2006-05-24 23:18 ` Junio C Hamano
2006-05-24 23:25 ` Shawn Pearce
2006-05-24 23:36 ` Shawn Pearce
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=20060524035234.GA13329@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).