From: Junio C Hamano <gitster@pobox.com>
To: Bruno Cesar Ribas <ribas@c3sl.ufpr.br>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] contrib/hooks/post-receive-email: checks for gitweb.description
Date: Sun, 17 Feb 2008 22:03:41 -0800 [thread overview]
Message-ID: <7vwsp2ssw2.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080218034659.GA21776@c3sl.ufpr.br> (Bruno Cesar Ribas's message of "Mon, 18 Feb 2008 00:46:59 -0300")
Bruno Cesar Ribas <ribas@c3sl.ufpr.br> writes:
> Forgoten?! 8^)
> On Tue, Feb 12, 2008 at 10:24:40PM -0200, Bruno Cesar Ribas wrote:
>> I can resend with no problem =)
More like "not so much interested myself, although I did not
have strong objection either".
Typically original author or people who would see much value in
the patch than myself have more incentive and motivation to keep
pushing for inclusion of such a patch, so I tend to trust them
to re-send saying "Here is the final for inclusion, the list
concensus was favorable, and I addressed all the issues raised
during the discussion." if they still care about the patch than
actively fishing for old patches from my mailbox.
On the other hand if such re-push never happens that is a good
indication that nobody is convinced strongly enough to stand
behind the patch, and my time is better spent elsewhere.
next prev parent reply other threads:[~2008-02-18 6:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 3:25 [PATCH] contrib/hooks/post-receive-email: checks for gitweb.description Bruno Ribas
2008-02-12 8:17 ` Jakub Narebski
2008-02-13 0:24 ` Bruno Cesar Ribas
2008-02-18 3:46 ` Bruno Cesar Ribas
2008-02-18 6:03 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-11 20:02 Bruno Ribas
2008-02-11 21:20 ` Jakub Narebski
2008-02-11 21:49 ` BRUNO CESAR RIBAS
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=7vwsp2ssw2.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=ribas@c3sl.ufpr.br \
/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).