From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] buildroot: Remove old CVS relics.
Date: Thu, 3 Sep 2009 22:58:23 +0200 [thread overview]
Message-ID: <20090903205823.GF28419@mx.loc> (raw)
In-Reply-To: <87a5b0800909031230l5ff046fen9778986b855aae76@mail.gmail.com>
On Thu, Sep 03, 2009 at 08:30:44PM +0100, Will Newton wrote:
>I considered doing this, I'm not sure what the best way is. I don't
>think we always want to follow the latest version but expressing an
For these particular 2 packages we do (since the risk is quite low, from
my experience). YMMV.
>upstream version as a git hash is not very friendly, there aren't many
>tags in the upstream repo.
That's why we had a local co that we could pull upon need.
Perhaps you can try if that works out fine?
prev parent reply other threads:[~2009-09-03 20:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 16:04 [Buildroot] [PATCH] buildroot: Remove old CVS relics Will Newton
2009-09-03 16:13 ` Bernhard Reutner-Fischer
2009-09-03 16:29 ` Will Newton
2009-09-03 17:19 ` Bernhard Reutner-Fischer
2009-09-03 17:15 ` Will Newton
2009-09-03 17:27 ` Bernhard Reutner-Fischer
2009-09-03 19:30 ` Will Newton
2009-09-03 20:58 ` Bernhard Reutner-Fischer [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=20090903205823.GF28419@mx.loc \
--to=rep.dot.nop@gmail.com \
--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