All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@openembedded.org
Subject: Re: git and dir
Date: Thu, 14 Aug 2008 07:03:48 -0500	[thread overview]
Message-ID: <48A41F24.1070507@dls.net> (raw)
In-Reply-To: <g815ta$ca0$1@ger.gmane.org>

Rolf Leggewie wrote:
> Phil Blundell wrote:
>> What's the specific corruption that you're worried about?
> 
> Maybe my worries are unfounded and that would be great.  I was thinking
> that building for a certain distribution but changing the checked out
> repo underneath its feet back and forth could eventually result in
> incompatible stuff getting into TMPDIR and particularly staging.  Think
> switching between dev, stable, openmoko and some of its variant and
> building stuff in between.  I don't think it is too far-fetched to worry
> this might lead to some incompatabilities in what is under TMPDIR.

I see both sides of this discussion.  Rolf brings up a very valid point;
a well-intentioned "newbie" may waste a lot of their time -- and the
time of others offering assistance.  On the other hand, I can see many
cases where switching about on minor branches would be useful, and if
one knows what they are doing, it could be a huge timesaver if TMPDIR
could be reused.

So can we consider a middle ground?  A warning message issued if the
current branch doesn't match the one recorded inside TMPDIR?  This could
be ignored by the experts, but it would be something easy to spot in
(for example) a pastebin offered by a struggling "non-expert" user.

Regarding the specific issue -- the openmoko users have already observed
cases where TMPDIR becomes non-useful because they thought they could
switch among branches/repos without penalty, resulting in incorrect
versions in staging, and other build issues.

Regards,
Mike (mwester)



  parent reply	other threads:[~2008-08-14 12:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 23:33 git and dir Rolf Leggewie
2008-08-14  7:41 ` Phil Blundell
2008-08-14 11:45   ` Rolf Leggewie
2008-08-14 12:02     ` Phil Blundell
2008-08-14 12:03     ` Mike (mwester) [this message]
2008-08-14 12:22       ` Rolf Leggewie
2008-08-14  9:34 ` Florian Boor

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=48A41F24.1070507@dls.net \
    --to=mwester@dls.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.