From: Junio C Hamano <junkio@cox.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC 2/5] Improve abstraction of ref lock/write.
Date: Wed, 17 May 2006 03:46:50 -0700 [thread overview]
Message-ID: <7vk68lgc85.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060517095502.GC28529@spearce.org> (Shawn Pearce's message of "Wed, 17 May 2006 05:55:02 -0400")
Shawn Pearce <spearce@spearce.org> writes:
> Created 'struct ref_lock' to contain the data necessary to perform
> a ref update...
>
> fetch.c | 32 +++++----
> refs.c | 236 ++++++++++++++++++++++++++++++---------------------------------
> refs.h | 24 ++++--
> 3 files changed, 144 insertions(+), 148 deletions(-)
Looks a bit intrusive probably necessary so not necessarily bad
but I'll postpone looking at this for now; maybe tomorrow or
more likely over the weekend.
Eyeballs from people touched the affected files in the past are
greatly appreciated.
prev parent reply other threads:[~2006-05-17 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 9:55 [RFC 2/5] Improve abstraction of ref lock/write Shawn Pearce
2006-05-17 10:46 ` Junio C Hamano [this message]
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=7vk68lgc85.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).