From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Jan Lübbe" <jlu@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: scripts/remote: make clean leftovers
Date: Wed, 3 Feb 2016 08:55:43 +0100 [thread overview]
Message-ID: <20160203075543.GJ4118@pengutronix.de> (raw)
In-Reply-To: <1453805349.2235.40.camel@pengutronix.de>
On Tue, Jan 26, 2016 at 11:49:09AM +0100, Jan Lübbe wrote:
> On Di, 2016-01-26 at 11:04 +0100, Yegor Yefremov wrote:
> > After performing make distclean I've discovered following files being removed:
> >
> > Changes not staged for commit:
> > (use "git add/rm <file>..." to update what will be committed)
> > (use "git checkout -- <file>..." to discard changes in working directory)
> >
> > deleted: scripts/remote/__init__.py
> > deleted: scripts/serial/tools/__init__.py
> > deleted: scripts/serial/urlhandler/__init__.py
> >
> > What should actually happen to these files?
>
> Python uses these files to recognize the directory as containing a
> module, so we need to keep them.
They get removed by make distclean, supposedly because they are empty.
What should they contain? Is it ok to put a comment in them to make them
non-empty?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-02-03 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 10:04 Yegor Yefremov
2016-01-26 10:49 ` Jan Lübbe
2016-02-03 7:55 ` Sascha Hauer [this message]
2016-02-03 8:58 ` Jan Lübbe
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=20160203075543.GJ4118@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jlu@pengutronix.de \
/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