public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Added a custodian status page to denx.de/UBoot
Date: Thu, 05 Apr 2007 08:16:05 -0400	[thread overview]
Message-ID: <4614E885.6090702@smiths-aerospace.com> (raw)
In-Reply-To: <000201c7776d$fde43300$821ba8c0@Emea.Arm.com>

Peter Pearse wrote:
>> -----Original Message-----
>> From: u-boot-users-bounces at lists.sourceforge.net 
>> [mailto:u-boot-users-bounces at lists.sourceforge.net] On Behalf 
>> Of Wolfgang Denk
>> Sent: 05 April 2007 01:25
>> To: Ben Warren
>> Cc: u-boot-users at lists.sourceforge.net; Jerry Van Baren
>> Subject: Re: [U-Boot-Users] Added a custodian status page to 
>> denx.de/UBoot
>>
>> In message <891383.24029.qm@web313.biz.mail.mud.yahoo.com> you wrote:
>>>> I think you should use branches on your local repository, 
>> but not  
>>>> on the custodian repo. There, I want to see no branches.
>>>>
>>> Hmmm.  I thought branches would provide an excellent way of putting 
>>> experimental code 'out there'  (i.e.
>>> code that's not intended for short-term upstream merging).  Is this 
>>> bad?
> 
> Wolfgang
> 	Now I believe I can push branches to the u-boot-arm repo 
> 
> (I was reading gu-arm as git-arm - I should use bigger fonts.....)
> 
> I was hoping to push each patch that I approved up to the u-boot-arm as a
> branch,
> for others to test.
>  
> Then I would ask you to merge from it when testing was complete.
> 
> Then I would delete that branch when merged.....
> 
> Peter

I would like to give branches a chance.  They have been supported since 
RCS (or before) so most people are familiar with the concept, if perhaps 
not the actual use.  I find branches in git are very usable and 
extremely useful.

I've added a section describing the use and status of (the) branch(es) 
in my custodian repository:
   <http://www.denx.de/wiki/UBoot/UBootFdtInfo>
Now I can simply reply "RTFM" (as if /that/ ever worked ;-).

gvb

  reply	other threads:[~2007-04-05 12:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-04 21:01 [U-Boot-Users] Added a custodian status page to denx.de/UBoot Jerry Van Baren
2007-04-04 22:54 ` Wolfgang Denk
2007-04-05  0:03   ` Ben Warren
2007-04-05  0:24     ` Wolfgang Denk
2007-04-05 10:34       ` Peter Pearse
2007-04-05 12:16         ` Jerry Van Baren [this message]
2007-04-05 14:15           ` Wolfgang Denk
2007-04-05 14:09         ` Wolfgang Denk
2007-04-05 14:31           ` Jerry Van Baren
2007-04-05 14:56             ` Jerry Van Baren
2007-04-05 14:56             ` Ben Warren
2007-04-05 15:21               ` Aubrey Li
2007-04-05 19:16                 ` Wolfgang Denk
2007-04-06  0:56                   ` Aubrey Li
2007-04-12 19:20                     ` Haavard Skinnemoen
2007-04-05 17:25               ` Jerry Van Baren

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=4614E885.6090702@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.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