public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Aubrey Li <aubrey.adi@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] FW: New port Siemens SMN42 board
Date: Wed, 21 Mar 2007 23:34:38 +0800	[thread overview]
Message-ID: <27d85ee10703210834r130fd301ycdcfcfcba88cd6a0@mail.gmail.com> (raw)
In-Reply-To: <20070321145330.F2089352636@atlas.denx.de>

On 3/21/07, Wolfgang Denk <wd@denx.de> wrote:
> In message <27d85ee10703210748n53202b12w7e1c35c502a4fe5d@mail.gmail.com> you wrote:
> >
> > > AFAIK I cant construct branches on the U-Boot server.
> > > I wanted to make a branch for each patch I was working with, so
> > > users/testers could access them.
> > > I can do that on our wiki server. So I made the tracking table there as
> > > well.
> > >
> > That's a good question. So what is the right way to maintain patches
> > which are not common enough to be committed into the master branch of
> > the git repository, but they are really useful. It would be better to
> > make them available to the user.
>
> I see no principal problem why branches should not be possible.
>
> You can give "pit push" a refspec as argument to select a specific
> branch, and you can use "--all" to push all refs.
>
> But I have to admit that I never tested this yet (which is  thereason
> why I did not reply on Peter's remark yet).
>
Yes, I tried just now and it works.
I created a branch named "blackfin" from current master branch.
I think this can satisfy Peter's requirement.

Best Regards,
-Aubrey

      reply	other threads:[~2007-03-21 15:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 14:57 [U-Boot-Users] FW: New port Siemens SMN42 board Peter Pearse
2007-03-19 15:39 ` Wolfgang Denk
2007-03-19 16:16   ` Peter Pearse
2007-03-21 14:48     ` Aubrey Li
2007-03-21 14:53       ` Wolfgang Denk
2007-03-21 15:34         ` Aubrey Li [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=27d85ee10703210834r130fd301ycdcfcfcba88cd6a0@mail.gmail.com \
    --to=aubrey.adi@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