All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: git and dir
Date: Thu, 14 Aug 2008 01:33:17 +0200	[thread overview]
Message-ID: <g7vqvs$3fi$1@ger.gmane.org> (raw)

Hi,

this is something I've been pondering upon today.  I'm hoping for some 
discussion, an opportunity to learn and possibly to make OE even better.

It has always been possible to shoot yourself in the foot with OE.  I 
believe the opportunities will rise with the introduction of git.  The 
reason is that AFAIU, with mtn there was a 1:1 relation between checkout 
dir and upstream branch.  This information was recorded in _MTN/options. 
  git does not have this restriction.  One can freely add remote 
branches to an existing checkout with "git remote add" and switch to 
them with "git checkout $branch".  This can easily corrupt tmp/ and I 
fear it will happen quite often.  I wonder if there is anything 
OE/bitbake can do to alleviate the pain.

Regards

Rolf


PS: I am just thinking if it made sense to add the possibility to 
include the git branch name in TMPDIR just like we can include DISTRO 
now.  I think that would go a long way towards making problems to occur 
only seldomly if at all.




             reply	other threads:[~2008-08-13 23:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 23:33 Rolf Leggewie [this message]
2008-08-14  7:41 ` git and dir Phil Blundell
2008-08-14 11:45   ` Rolf Leggewie
2008-08-14 12:02     ` Phil Blundell
2008-08-14 12:03     ` Mike (mwester)
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='g7vqvs$3fi$1@ger.gmane.org' \
    --to=no2spam@nospam.arcornews.de \
    --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.