From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] StGit patch series import
Date: Mon, 25 May 2009 00:18:25 +0200 [thread overview]
Message-ID: <cb7bb73a0905241518l43048416i34cb905c143c63e0@mail.gmail.com> (raw)
In-Reply-To: <7vfxeurwh0.fsf@alter.siamese.dyndns.org>
On Mon, May 25, 2009 at 12:02 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Giuseppe Bilotta <giuseppe.bilotta@gmail.com> writes:
>
>> That was my initial thought too, but then I realized that having the
>> 'heuristics' (although a very braindead one) in mailinfo makes more
>> sense because otherwise StGIT patch autodetection would only work when
>> applying a whole series, and not when applying a single (or a few)
>> patches.
>
> The above is very selfish---what if somebody else wanted to add a feature
> to grok a non-mailbox input to the same codepath, and it is not a StGIT
> patch?
>
> That is what I called "bad taste".
>
> The same comment may apply to the rest of your response. "This hack is
> good enough for _my_ use case; I do not care if my change makes life
> harder for others to build on top of my patch" is not what I want to see.
Sorry, that's totally not the idea was trying to convey. In fact, just
after sending the email I went back to the code to look for a better
solution (I should have probably also made the first try a RFC).
I did feel it was necessary to explain the reasons for the simplicity
of the patches, especially since it gave me the chance to raises some
points that I thought were worth discussing, such as the matter of
where to place patch type autodetection.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2009-05-24 22:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 7:19 [PATCH 0/2] StGit patch series import Giuseppe Bilotta
2009-05-24 20:49 ` Junio C Hamano
2009-05-24 21:43 ` Giuseppe Bilotta
2009-05-24 21:55 ` Sverre Rabbelier
2009-05-24 22:04 ` Giuseppe Bilotta
2009-05-24 22:05 ` Sverre Rabbelier
2009-05-24 22:02 ` Junio C Hamano
2009-05-24 22:18 ` Giuseppe Bilotta [this message]
2009-05-24 22:28 ` Sverre Rabbelier
2009-05-24 22:53 ` Giuseppe Bilotta
2009-05-24 22:57 ` Sverre Rabbelier
2009-05-24 23:03 ` Giuseppe Bilotta
2009-05-25 6:39 ` Junio C Hamano
2009-05-25 7:19 ` Giuseppe Bilotta
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=cb7bb73a0905241518l43048416i34cb905c143c63e0@mail.gmail.com \
--to=giuseppe.bilotta@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).