public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marko Mikulicic <marko@seul.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Contribute many ebuilds at once
Date: Sun, 09 Jun 2002 02:41:44 -0400	[thread overview]
Message-ID: <3D02F8A8.7030108@seul.org> (raw)
In-Reply-To: Pine.LNX.3.96.1020609021600.11015B-100000@pluto.prosalg.no

Karl Trygve Kalleberg wrote:
>>I must admit my hatered on web-interfaces and this kind of
>>repeatitive work.
>>
> 
> Depending on how important you feel it is that your ebuilds go into CVS
> asap, you might want to hold for two more weeks, and help test a new,
> prototype ebuild submission system where you can submit from your
> commandline, or even text-mode webbrowser :)

I want just to avoid duplicate work, in case someone feels
the need to use, say wmtop, and than wm*; sure they are
nice apps to start understanding portage, because they are small,
but if someone already did that three weeks ago without telling .... 
aargh :-)

I would like to help developing a flexible command line submission system.
I'm interested in how are you currently organized, how and who read the
"bug" submissions ...
  Alternatively I could write a dummy client which connects to the 
bugzilla like a webbrowser and automates the submission.
  (I suppose there is not a secure straight connection to the bugzilla 
backend)
  I see all this by a user perspective, not as a maintainer; so I would
like to learn more.

Marko





  parent reply	other threads:[~2002-06-09  0:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-09  6:07 [gentoo-dev] Contribute many ebuilds at once Marko Mikulicic
2002-06-09  0:18 ` Karl Trygve Kalleberg
2002-06-09  0:53   ` Jano Lukac
2002-06-09  6:55     ` Marko Mikulicic
2002-06-09 15:41     ` Karl Trygve Kalleberg
2002-06-09  6:41   ` Marko Mikulicic [this message]
2002-06-09 10:56     ` Paul de Vrieze
2002-06-09 17:35       ` Marko Mikulicic
2002-06-09 12:25         ` Jeremiah Mahler
2002-06-09 15:29           ` Markus Krainer
2002-06-09 18:46           ` Marko Mikulicic
2002-06-09 14:40             ` Jeremiah Mahler
2002-06-09 21:21               ` Marko Mikulicic
2002-06-09 18:53                 ` George Shapovalov
2002-06-09 19:57                   ` Karl Trygve Kalleberg
2002-06-09 15:56         ` Karl Trygve Kalleberg
2002-06-09 19:31       ` Marko Mikulicic
2002-06-09 15:39     ` Karl Trygve Kalleberg
2002-06-09 21:53       ` Marko Mikulicic
2002-06-09 16:03         ` Karl Trygve Kalleberg
2002-06-09 16:17           ` Markus Krainer
2002-06-10  0:54             ` Marko Mikulicic
2002-06-09 19:53               ` Karl Trygve Kalleberg
2002-06-09 21:37               ` [gentoo-dev] cvs keywords (was: Contribute many ebuilds at once) Alexander Holler
2002-06-10  3:46                 ` Marko Mikulicic
2002-06-09 22:25                   ` [gentoo-dev] cvs keywords Alexander Holler
2002-06-10  7:41                     ` Marko Mikulicic
2002-06-09 22:11           ` [gentoo-dev] Contribute many ebuilds at once Marko Mikulicic
2002-06-09 19:52             ` Karl Trygve Kalleberg
2002-06-09 21:04             ` [gentoo-dev] cvs keywords (was: Contribute many ebuilds at once) Alexander Holler
2002-06-10  1:33               ` Markus Krainer
2002-06-10  0:50       ` [gentoo-dev] Contribute many ebuilds at once Justin Lambert

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=3D02F8A8.7030108@seul.org \
    --to=marko@seul.org \
    --cc=gentoo-dev@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