public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Buildman cookbook
Date: Wed, 29 Oct 2014 19:04:41 +0100	[thread overview]
Message-ID: <54512C39.3040603@gmail.com> (raw)
In-Reply-To: <CAPnjgZ0HbeoOkb9A-USBjMXh39qJFdmATf8W7DZb4Qj_jFYWmA@mail.gmail.com>

Hi Simon,

>>
>> - I work a lot with local branches, and regularly run into this:
>>
>>   -> tools/buildman/buildman -n -b tq-generic-board
>>   No section: 'make-flags'
>>   Branch 'tq-generic-board' not found or has no upstream
>>
>>   Can we not avoid this?  Or add a default to "master"?
> 
> I think we might be able to have a default. How did you create the
> local branch? I normally use:
> 
> git checkout -b my-branch upstream/master
> 
> and it does the right thing.
> 
>>
>>   The README recommends to use "git branch --set-upstream ...", but
>>   actually I don't want to do that - it is simply not needed.
>>   Furthermore, git complains;
>>
>>   -> git branch --set-upstream tq-generic-board master
>>   The --set-upstream flag is deprecated and will be removed. Consider using --track or --set-upstream-to
>>   Branch tq-generic-board set up to track local branch master.
> 
> Yes I notice that in recent versions. We probably need another round
> of tweaks although I mostly have my hands full for a few weeks.
> 

it would be nice if one can specify branch ranges. For example:

tools/buildman/buildman -b master..my_feature
tools/buildman/buildman -b origin/master..master

-- 
- Daniel

      parent reply	other threads:[~2014-10-29 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27  9:04 [U-Boot] Buildman cookbook Wolfgang Denk
2014-10-29 15:09 ` Simon Glass
2014-10-29 15:15   ` Dirk Eibach
2014-10-29 15:29   ` Wolfgang Denk
2014-10-29 18:04   ` Daniel Schwierzeck [this message]

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=54512C39.3040603@gmail.com \
    --to=daniel.schwierzeck@gmail.com \
    --cc=u-boot@lists.denx.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