From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] \" fixes
Date: Sat Aug 11 03:18:02 2001 [thread overview]
Message-ID: <871ymjlzyt.fsf@codefactory.se> (raw)
In-Reply-To: <20010810233655.D24185@cvs.gentoo.org>
Hi!
I think it would be good if someone (Aron?) could post a short version
of Aron's mail (which by the way was well written and interesting
reading, thanks) to describe when to use which for those that hasn't
read it (it was also long :). One without the technical internals of
the commands. Just a quick description and an example of each.
Regards,
Mikael Hallendal
Daniel Robbins <drobbins@gentoo.org> writes:
> Hi All,
>
> I just all the ebuilds on CVS that needed \" fixes due to an upgrade
> of the "try" command (about 50). This means that everyone should
> rsync/cvs update and remerge Portage, even if you've done so in the
> past few days. This means that developers can now type:
>
> try make COPT="$CFLAGS"
>
> rather than the old way:
>
> try make COPT=\"$CFLAGS\"
>
> Also, Aron Griffis' "die" and "assert" commands are now part of the
> Portage currently on CVS, and developers should start transitioning to
> these new commands as they're much better than "try".
>
> Best Regards,
>
> --
> Daniel Robbins <drobbins@gentoo.org>
> Chief Architect/President http://www.gentoo.org
> Gentoo Technologies, Inc.
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
--
Mikael Hallendal micke@codefactory.se
CodeFactory AB http://www.codefactory.se/
Office: +46 (0)8 587 583 05 Cell: +46 (0)709 718 918
next prev parent reply other threads:[~2001-08-11 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 23:37 [gentoo-dev] \" fixes Daniel Robbins
2001-08-11 3:18 ` Mikael Hallendal [this message]
2001-08-12 2:43 ` [gentoo-dev] how to use die() and assert_true_or_die() Chris Houser
2001-08-12 12:59 ` Daniel Robbins
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=871ymjlzyt.fsf@codefactory.se \
--to=hallski@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.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