From: Junio C Hamano <junkio@cox.net>
To: Carl Worth <cworth@cworth.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-ls-files: Fix, document, and add test for --error-unmatch option.
Date: Tue, 21 Feb 2006 17:59:31 -0800 [thread overview]
Message-ID: <7vr75wtapo.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 87vev8sajl.wl%cworth@cworth.org
Carl Worth <cworth@cworth.org> writes:
> I'm still not sure what the easiest way is for me to provide changes
> to you. I've been doing it here on the list, like with the current
> message. But would it be easier for me to send pull requests?
You can decide what is easier for _you_ ;-).
But for me, emailed patches are easier to work on than pull
requests. I will need to read and understand most of the
changes anyway, unless the change is to an isolated corner of
the system that would affect only one class of users and
breakage will be noticed either immediately or can be left
broken if nobody uses that (e.g. things like contrib/ and some
foreign SCM interfaces). I would like others on the list to be
able to review the same changes that might hit my tree and
provide extra sets of eyeballs to spot things I might miss
myself alone.
> For example, with the git-clone failure cleanup I recently did, it
> seems the new test case I wrote didn't land in your tree.
Sorry, I think I just forgot to apply that one. I still have
the message so no need to resend. Thanks for reminding.
prev parent reply other threads:[~2006-02-22 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 20:48 [PATCH] git-ls-files: Fix, document, and add test for --error-unmatch option Carl Worth
2006-02-22 1:59 ` 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=7vr75wtapo.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=cworth@cworth.org \
--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).