public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: New mtd-utils release?
Date: Mon, 14 Dec 2009 22:34:35 +0800	[thread overview]
Message-ID: <20091214143435.GD28375@buzzloop.caiaq.de> (raw)
In-Reply-To: <1260795633.11112.49.camel@localhost>

On Mon, Dec 14, 2009 at 03:00:33PM +0200, Artem Bityutskiy wrote:
> On Mon, 2009-12-14 at 20:14 +0800, Daniel Mack wrote:
> > we're building mtd-utils with buildroot, and as we need a recent version
> > of it to get the ubi features, we currently check out a git snapshot as
> > tarball. Last week, for some reason the SHA1 ID we used (e783e75e0)
> > disappeared from the repository. (Just out of curiosity: what happened?
> > Was the tree rebased or filtered?).
> 
> Dunno, but it must be me how made this crew-up, sorry. I cannot say
> exactly how it happened, but it was non-intentional. Probably pushed one
> patch version, then later amended it, and pushed it with --force. This
> should never be done, sorry.

No big thing, I was just wondering. Probably the commit was dead (ie,
not lined-up with an exposed head) for a longer time and just got
vacuumed last week, dunno.

> > However, this approach is somewhat hackish anyway, and we would much
> > more like to check out a version that is officially tagged.
> 
> OK, I can tag them at the beginning of the next year. I'm having
> holydays in 10 min.
> 
> >  Seeing the
> > last tag has been done ~17 month ago, I wonder whether there is any
> > change to get a new one soon?
> 
> We usually use the master branch. And there is simply no one who cares
> about tags. But I can do this. You'll get a new tag when I come back
> from holydays, unless someone else tag it earlier.

Great, thank you. The background of my question was also whether there
is a version which is reliable, in terms of representing a stable set
of features, defining a larger merge of new features and the like, so
it deserves the term 'release' :)

Not saying that any of the snapshops caused any trouble so far, it would
just feel better to check out something that has been tagged by the
maintainers.

Thanks,
Daniel

      parent reply	other threads:[~2009-12-14 14:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 12:14 New mtd-utils release? Daniel Mack
2009-12-14 12:48 ` Peter Korsgaard
2009-12-14 13:00 ` Artem Bityutskiy
2009-12-14 13:03   ` Peter Korsgaard
2010-01-04  7:42     ` Artem Bityutskiy
2010-01-04  8:11       ` Peter Korsgaard
2010-01-04 21:25       ` Robert Schwebel
2010-01-05  6:21         ` Artem Bityutskiy
2010-01-05  8:37           ` Peter Korsgaard
2010-01-05  8:43             ` David Woodhouse
2010-01-19 14:53               ` Peter Korsgaard
2010-01-05  8:44             ` Artem Bityutskiy
2010-01-05  8:50               ` Peter Korsgaard
2010-01-05 11:42             ` Jamie Lokier
2009-12-14 13:56   ` Josh Boyer
2009-12-14 14:41     ` Peter Korsgaard
2009-12-14 15:59       ` Josh Boyer
2009-12-16 11:56         ` OMAP2 issue while compiling the latest mtd-2.6 git kernel Tadimarri Sarath Babu
2010-01-07  6:47           ` Artem Bityutskiy
2009-12-14 14:34   ` Daniel Mack [this message]

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=20091214143435.GD28375@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.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