From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mtd-utils: bump version number
Date: Mon, 14 Dec 2009 12:32:45 +0100 [thread overview]
Message-ID: <87hbrtssde.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20091214104935.GA28375@buzzloop.caiaq.de> (Daniel Mack's message of "Mon, 14 Dec 2009 18:49:35 +0800")
>>>>> "Daniel" == Daniel Mack <daniel@caiaq.de> writes:
Hi,
Daniel> Ok, the master branch moved forward and I recognized that too late,
Daniel> hence the two patches.
Ok.
>> It would be nice if the shortname could be computed from MTD_VERSION so
>> things don't break when someone goes and changes the git id. GNU make
>> unfortunately doesn't have a substring function, so the easiest solution
>> is probably cut, E.G.:
Daniel> I though about that too, but I wasn't sure whether the substring of the
Daniel> SHA1 ID would always be 7 characters long. I fear that is choses to be
Daniel> as short as possible but as long as necessary to be unique. Which would
Daniel> then mean that it changes again at an aribitrary point.
Currently it is (gitweb calls git rev-parse --short-7), but I get your
point. This gitweb change is also very recent (since 1.6.6-rc1, released
December 2nd). I'll add a comment about it.
Daniel> Best thing woulod be if the mtd people would just tag a commit with a
Daniel> new release number. I'll write them and see if I can make them do that
Daniel> :)
Yes, please - It has been 17 months since the last release, so it's
about time.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-12-14 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 23:45 [Buildroot] [PATCH] mtd-utils: bump version number Daniel Mack
2009-12-11 23:55 ` Daniel Mack
2009-12-14 9:49 ` Peter Korsgaard
2009-12-14 10:49 ` Daniel Mack
2009-12-14 11:32 ` Peter Korsgaard [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=87hbrtssde.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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