mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: is there a standard for putting the name of a source file in the file?
Date: Mon, 19 Nov 2012 10:41:01 +0100	[thread overview]
Message-ID: <20121119094101.GK10369@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1211181139290.32036@oneiric>

On Sun, Nov 18, 2012 at 11:39:48AM -0500, Robert P. J. Day wrote:
> On Sun, 18 Nov 2012, Jean-Christophe PLAGNIOL-VILLARD wrote:
> 
> > On 08:48 Sun 18 Nov     , Robert P. J. Day wrote:
> > >
> > >   as i'm working my way thru the lib/ routines in barebox, i notice
> > > that some source files there, like getopt.c, conveniently have the
> > > filename right at the top:
> > >
> > > /*
> > >  * getopt.c - a simple getopt(3) implementation. See getopt.h for explanation.
> > > ...
> > >
> > > i really like this habit as it makes it easy to send a file to the
> > > printer and not forget what the file was.
> > >
> > >   however, most of the files in lib/ don't have that.  as i work my
> > > way through the files, i'd be happy to add something like that to each
> > > file, and submit the changes all as one patch.  is there a standard?
> > > from what i can see, there's quite the variety in how people add that
> > > to a source file.
> > >
> > >   i'm open to guidance and i can take it from there.
> > no this is a pain in the ass to maintian when we move file
> >
> > I' drop it and I'm against it
> 
>   ok, that logic makes sense, i'm good with that.

Me aswell. Tools like a2ps also print the filename ;)

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

  reply	other threads:[~2012-11-19  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18 13:48 Robert P. J. Day
2012-11-18 16:26 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-18 16:39   ` Robert P. J. Day
2012-11-19  9:41     ` Sascha Hauer [this message]
2012-11-19  9:46       ` Robert P. J. Day

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=20121119094101.GK10369@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=rpjday@crashcourse.ca \
    /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