public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jacob Godserv <jacobgodserv@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [bugzilla-daemon@gentoo.org: [Bug 322157]  [mail-filter/procmail] new ebuild + autocreate maildirs]
Date: Sun, 11 Jul 2010 01:28:21 -0400	[thread overview]
Message-ID: <AANLkTimQcffQSKh6k0KT-ryaFbiCsNWK-m43GGJD1rIJ@mail.gmail.com> (raw)
In-Reply-To: <20100710161343.GC15161@nibiru.local>

On Sat, Jul 10, 2010 at 12:13, Enrico Weigelt <weigelt@metux.de> wrote:
> I've already explained the strategy behind the git repo (and not
> doing plaintext patches). Please refer to my paper, and my other
> mails posted recently on this list.

I'm not quite sure I understand your response here. He didn't ask for
you to explain the strategy. He asked for you to provide plain-text
patches.

I think a point has been made pretty clear at this point: they need
plain-text patches. Requiring developers to learn an entirely new
work-flow just to get your patches into the tree is time-consuming and
bothersome, at the least. This isn't a discussion about whether or not
your system is better. It's about how best to integrate your work into
Gentoo.

The developers have decided the best way is through plain-text
patches. That's really all there is to it. Take it or leave it.

The discussion about how best to join multiple branches of development
across the open-source world together really does not belong in this
thread, as far as I can tell.

-- 
    Jacob

    "For then there will be great distress, unequaled
    from the beginning of the world until now — and never
    to be equaled again. If those days had not been cut
    short, no one would survive, but for the sake of the
    elect those days will be shortened."

    Are you ready?



  reply	other threads:[~2010-07-11  5:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 22:56 [gentoo-dev] [bugzilla-daemon@gentoo.org: [Bug 322157] [mail-filter/procmail] new ebuild + autocreate maildirs] Enrico Weigelt
2010-07-07 23:11 ` Samuli Suominen
2010-07-10 16:13   ` Enrico Weigelt
2010-07-11  5:28     ` Jacob Godserv [this message]
2010-07-11  7:01       ` Hans de Graaff
2010-07-11  7:09         ` Enrico Weigelt
2010-07-11  8:58           ` Nirbheek Chauhan
2010-07-11  9:51             ` [gentoo-dev] " Duncan
2010-07-11  9:53             ` [gentoo-dev] " Enrico Weigelt
2010-07-11 10:28               ` Nirbheek Chauhan
2010-07-11 16:53                 ` Jorge Manuel B. S. Vicetto
2010-07-12  2:54                   ` Enrico Weigelt
2010-07-12  2:44                 ` Enrico Weigelt
2010-07-12 11:55                   ` Nirbheek Chauhan
2010-07-15 13:43                     ` Enrico Weigelt
2010-07-08  0:03 ` [gentoo-dev] Re: [funtoo] [bugzilla-daemon-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org: " Ryan Hill
2010-07-12  5:25   ` Nathan Phillip Brink
2010-07-08  1:36 ` [gentoo-dev] [bugzilla-daemon@gentoo.org: " Robin H. Johnson
2010-07-10 16:07   ` Enrico Weigelt
2010-07-08  2:38 ` [gentoo-dev] Re: [funtoo] [bugzilla-daemon-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org: " Paul Arthur

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=AANLkTimQcffQSKh6k0KT-ryaFbiCsNWK-m43GGJD1rIJ@mail.gmail.com \
    --to=jacobgodserv@gmail.com \
    --cc=gentoo-dev@lists.gentoo.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