From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: preview of "What's cooking" (topics)
Date: Wed, 03 Jan 2007 02:25:03 -0800 [thread overview]
Message-ID: <7virfopfuo.fsf@assigned-by-dhcp.cox.net> (raw)
My git day this week hasn't started yet, but for people to base
their improvements on, here is a quick status before I go to
bed.
- Detached HEAD along with two patches to teach git-status and
git-branch about not being on any branch are in 'pu'; I
removed -d option from git-checkout from the previous round.
- Jürgen's git-status improvements are mostly in 'next' but
one of them is queued in 'pu', waiting for comments.
- I've queued my counterproposal to Shawn's lockfile fix in
'pu', waiting for comments.
On the 'master' front, I've merged Andy's xwrite() loop. I
think this is applicable to many other places after generalizing
it a bit more and perhaps merging it with safe_write in
pkt-line.c.
builtin-apply.c, builtin-unpack-objects.c, copy.c, csum-file.c,
index-pack.c, merge-recursive.c and pkt-line.c have
implementations of something very similar, with different policy
on error handling.
Also index-pack.c and upload-pack.c (in the status reporting
code path) also has unprotected xwrite() that can result in
short write.
Have fun.
next reply other threads:[~2007-01-03 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 10:25 Junio C Hamano [this message]
2007-01-03 23:08 ` preview of "What's cooking" (topics) Juergen Ruehle
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=7virfopfuo.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox