mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Premi, Sanjeev" <premi@ti.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: RE: "make distclean" doesn't remove generated MLO file
Date: Tue, 7 Feb 2012 17:27:35 +0000	[thread overview]
Message-ID: <E28AAFD00EFAA646AE3DF9B89CD24A893183453E@DBDE01.ent.ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1202071206120.17030@oneiric>

> -----Original Message-----
> From: Robert P. J. Day [mailto:rpjday@crashcourse.ca] 
> Sent: Tuesday, February 07, 2012 10:38 PM
> To: Premi, Sanjeev
> Cc: U-Boot Version 2 (barebox)
> Subject: RE: "make distclean" doesn't remove generated MLO file
> 
> On Tue, 7 Feb 2012, Premi, Sanjeev wrote:
> 
> > > -----Original Message-----
> > > From: Robert P. J. Day [mailto:rpjday@crashcourse.ca]
> > > Sent: Tuesday, February 07, 2012 10:33 PM
> > > To: Premi, Sanjeev
> > > Cc: U-Boot Version 2 (barebox)
> > > Subject: RE: "make distclean" doesn't remove generated MLO file
> > >
> > > On Tue, 7 Feb 2012, Premi, Sanjeev wrote:
> > >
> > > > I usually compile both stages together with a 'make clean' in
> > > > between, hence decided to preserve MLO. Makes it easy 
> to copy both
> > > > MLO and barebox.bin at same time.
> > >
> > >   is there any sort of requirement about cleaning in 
> between those two
> > > steps?  if there is, that's a potential "gotcha" that should be
> > > clearly documented.
> >
> > No "gotcha" that I know of - but just a habit!
> 
>   i figured as much.  but under the circumstances, i think removing
> MLO should be part of CLEAN_FILES given its obvious relationship to
> things like barebox.bin.  philosophically, it just makes more sense.
> and on that note, i will now shut up about it.

I noted in earlier response:
  > Otherwise, yes, MLO goes better with CLEAN_FILES.
So, you are right.

Let us wait if there is any other opinion on this.

~sanjeev

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-02-07 17:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 13:19 Robert P. J. Day
2012-02-07 16:34 ` Premi, Sanjeev
2012-02-07 16:44   ` Robert P. J. Day
2012-02-07 16:59     ` Premi, Sanjeev
2012-02-07 17:02       ` Robert P. J. Day
2012-02-07 17:05         ` Premi, Sanjeev
2012-02-07 17:07           ` Robert P. J. Day
2012-02-07 17:27             ` Premi, Sanjeev [this message]
2012-02-07 21:59         ` Sascha Hauer

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=E28AAFD00EFAA646AE3DF9B89CD24A893183453E@DBDE01.ent.ti.com \
    --to=premi@ti.com \
    --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