From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Aditya Upadhyay <aadit0402@gmail.com>, newlib@sourceware.org
Subject: Re: Importing inttypes methods from FreeBSD
Date: Wed, 19 Jul 2017 09:34:00 -0000 [thread overview]
Message-ID: <167b4355-ad96-f0fe-0963-a514a6fa5928@embedded-brains.de> (raw)
In-Reply-To: <CAMZxAxca3drRUx1-wZEbZbCwQADsydO79OkyT-1vF-gty1-1yA@mail.gmail.com>
Hello Aditya Upadhyay,
for imports from FreeBSD, please use the SVN checkout and not the Git
mirror. This way you get an expansion of the
__FBSDID("$FreeBSD$");
This makes it easier to figure out the origin of imported files. It may help in case of future updates.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
next prev parent reply other threads:[~2017-07-19 9:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 21:40 Aditya Upadhyay
2017-07-19 9:34 ` Sebastian Huber [this message]
2017-07-19 10:16 ` Aditya Upadhyay
2017-07-19 10:58 ` Sebastian Huber
2017-07-19 12:28 ` Corinna Vinschen
2017-07-19 13:23 ` Aditya Upadhyay
2017-07-19 14:13 ` Craig Howland
2017-07-19 15:44 ` Corinna Vinschen
2017-07-19 17:00 ` Aditya Upadhyay
2017-07-20 8:25 ` Aditya Upadhyay
2017-07-20 14:37 ` Corinna Vinschen
2017-07-21 15:43 ` Gedare Bloom
2017-07-21 19:31 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2017-07-11 6:01 Aditya Upadhyay
2017-07-11 3:29 Aditya Upadhyay
2017-07-11 9:06 ` Corinna Vinschen
[not found] ` <CAMZxAxccBx9oDRiVE-mw5JEcKrLW4GKTdvg-dt+8bTHU=5j54w@mail.gmail.com>
2017-07-12 9:50 ` Aditya Upadhyay
2017-07-12 12:07 ` Corinna Vinschen
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=167b4355-ad96-f0fe-0963-a514a6fa5928@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=aadit0402@gmail.com \
--cc=newlib@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).