From: Michael Haggerty <mhagger@alum.mit.edu>
To: git@vger.kernel.org
Subject: 66 patches and counting
Date: Wed, 05 Oct 2011 23:29:57 +0200 [thread overview]
Message-ID: <4E8CCC55.9070408@alum.mit.edu> (raw)
My renovation of refs.c [1] is currently at 66 patches and counting.
What can I say?: (1) I like to make changes in the smallest irreducible
steps and (2) there is a lot that needed to be done in refs.c.
When I'm done, is it OK to dump a patch series like that on the git
mailing list? Is it pointless because nobody will review them anyway?
Is a big pile of changes like this welcome in any form? Would it be
better to convey the changes via git itself (e.g., github) rather than
via emails?
Michael
[1] hierarchical-refs at git://github.com/mhagger/git.git
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next reply other threads:[~2011-10-05 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 21:29 Michael Haggerty [this message]
2011-10-05 21:36 ` 66 patches and counting Junio C Hamano
2011-10-05 21:55 ` Jonathan Nieder
2011-10-06 22:16 ` Martin Fick
2011-10-07 1:59 ` Martin Fick
2011-10-07 3:14 ` Michael Haggerty
2011-10-07 15:51 ` Scalable reference handling Michael Haggerty
2011-10-07 18:51 ` Martin Fick
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=4E8CCC55.9070408@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--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;
as well as URLs for NNTP newsgroup(s).