From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aubrey Li Date: Wed, 21 Mar 2007 23:34:38 +0800 Subject: [U-Boot-Users] FW: New port Siemens SMN42 board In-Reply-To: <20070321145330.F2089352636@atlas.denx.de> References: <27d85ee10703210748n53202b12w7e1c35c502a4fe5d@mail.gmail.com> <20070321145330.F2089352636@atlas.denx.de> Message-ID: <27d85ee10703210834r130fd301ycdcfcfcba88cd6a0@mail.gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 3/21/07, Wolfgang Denk 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