All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: dedekind1@gmail.com
Cc: Bruno Cornec <bruno@project-builder.org>,
	linux-mtd@lists.infradead.org, twebb <taliaferro62@gmail.com>,
	David.Woodhouse@intel.com
Subject: Re: latest MTD-utils
Date: Tue, 21 Sep 2010 16:42:30 +0200	[thread overview]
Message-ID: <87mxrb17l5.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1285079252.7512.136.camel@localhost> (Artem Bityutskiy's message of "Tue, 21 Sep 2010 17:27:32 +0300")

>>>>> "Artem" == Artem Bityutskiy <dedekind1@gmail.com> writes:

Hi,

 Artem> It is not too difficult to provide tarball, but this is
 Artem> something developers do not care about, they develop. Packagers
 Artem> do care, and it is saner when packagers do this, not developers.

 Artem> I was in LinuxCon Brazil this year, and there was this presentation:
 Artem> http://events.linuxfoundation.org/2010/linuxcon-brazil/cornec

 Artem> where bruno said exactly the same. And he was promoting his
 Artem> project which claims to be able to pick sources from anywhere -
 Artem> git, svn, whatever.

 Artem> So the question is, why Buildroot cannot adjust to the reality
 Artem> (which is that developers in average do not care about tarballs)
 Artem> and cannot be improved?

Sure, buildroot can fetch from git - That's not the problem. All I'm
asking for is a bit of consistency to lower the amount of confusion:

- Either provide tarballs like in the past
- Or clearly state that you don't (website, readme on ftp site) and
  (re)move the old releases so people don't think that's where they are
  supposed to find releases (E.G. google for
  ftp://ftp.infradead.org/pub/mtd-utils/ and see the amount of references)

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2010-09-21 14:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20 22:47 latest MTD-utils twebb
2010-09-21  7:25 ` Artem Bityutskiy
2010-09-21 13:45   ` Peter Korsgaard
2010-09-21 13:51     ` Artem Bityutskiy
2010-09-21 13:54       ` Artem Bityutskiy
2010-09-21 14:07         ` Peter Korsgaard
2010-09-21 14:27           ` Artem Bityutskiy
2010-09-21 14:42             ` Peter Korsgaard [this message]
2010-09-23 12:03               ` Artem Bityutskiy
2010-09-23 12:13                 ` Peter Korsgaard
2010-09-22 22:47             ` Bruno Cornec
2010-09-21 15:24       ` David Woodhouse
2010-09-21 14:03     ` twebb

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=87mxrb17l5.fsf@macbook.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --cc=David.Woodhouse@intel.com \
    --cc=bruno@project-builder.org \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=taliaferro62@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.