public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Bryan Hundven <bryanhundven@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
	"andrew@ncrmnt.org" <andrew@ncrmnt.org>,
	"crossgcc@sourceware.org" <crossgcc@sourceware.org>,
	John Collis <John.Collis@alliedtelesis.co.nz>
Subject: Re: crosstool-NG Debian packaging
Date: Tue, 23 Feb 2016 15:41:00 -0000	[thread overview]
Message-ID: <D4D35A1B-534A-4EF4-9E3E-DF44FEA989ED@gmail.com> (raw)
In-Reply-To: <20160223140514.3b5eb69b@free-electrons.com>

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

Thomas,

> On Feb 23, 2016, at 5:05 AM, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> 
> Dear Chris Packham,
> 
> On Tue, 23 Feb 2016 03:55:07 +0000, Chris Packham wrote:
> 
>> I also notice that the tarball from github[1] has some unfortunate paths
>> in it, "crosstool-ng-crosstool-ng-1.22.0" which makes packaging it a bit
>> of a pain (1.21.0 also seems to have the same issue).
> 
> That's because Bryan uses "crosstool-ng-X.Y.Z" as tag names, so when
> github generates tarballs of the form <projectname>-<tagname> you get
> two times the crosstool-ng part. The tags should be named just X.Y.Z.

Technically, I am following the same convention that Yann E. MORIN did his tags, so ’s/Bryan/Yann/g’, but you are correct.
On the other hand, the archive release that github has does not have bootstrap ran, and is not GPG signed, therefore I recommend getting the archive from the crosstool-ng.org link instead… as I’ve already mentioned.

Cheers,

-Bryan

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]

  reply	other threads:[~2016-02-23 15:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 20:32 Chris Packham
2016-02-10 20:41 ` Bryan Hundven
2016-02-10 20:49   ` Chris Packham
2016-02-10 20:52     ` Bryan Hundven
2016-02-10 21:05       ` Chris Packham
2016-02-10 21:43 ` andrew
2016-02-23  3:55   ` Chris Packham
2016-02-23  4:37     ` Bryan Hundven
2016-02-23  4:40     ` Bryan Hundven
2016-02-23 21:15       ` Chris Packham
2016-02-23 13:05     ` Thomas Petazzoni
2016-02-23 15:41       ` Bryan Hundven [this message]
2016-02-23 21:26         ` Github tags (was Re: crosstool-NG Debian packaging) Chris Packham
2016-02-12  4:20 ` crosstool-NG Debian packaging Chris Packham
2016-02-12 19:49   ` Bryan Hundven
2016-02-14 19:42     ` Chris Packham

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=D4D35A1B-534A-4EF4-9E3E-DF44FEA989ED@gmail.com \
    --to=bryanhundven@gmail.com \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=John.Collis@alliedtelesis.co.nz \
    --cc=andrew@ncrmnt.org \
    --cc=crossgcc@sourceware.org \
    --cc=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).