From mboxrd@z Thu Jan  1 00:00:00 1970
From: Catalin Marinas <catalin.marinas@arm.com>
Date: Tue, 16 Aug 2005 17:22:37 +0100
Subject: [U-Boot-Users] Re: U-Boot Developer's Information
In-Reply-To: <20050816155948.3F75A353AB5@atlas.denx.de> (Wolfgang Denk's
 message of "Tue, 16 Aug 2005 17:59:48 +0200")
References: <20050816155948.3F75A353AB5@atlas.denx.de>
Message-ID: <tnxpssdlulu.fsf@arm.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Wolfgang Denk <wd@denx.de> wrote:
> In message <tnx3bpamca6.fsf@arm.com> you wrote:
>> 
>> Any plans to add a gitweb interface?
>
> Up and running. See http://source.denx.net/cgi-bin/gitweb.cgi

Great, thanks.

>> Contributors who are used to Quilt could also use StGIT as one of the
>> porcelains ('stg clone http://source.denx.net/git/u-boot.git u-boot').
>> It might simplify the patches maintenance/submission ('mail' command
>> available as well).
>
> True. I have to admit that I didn't look into StGIT yet - do you  use
> it? Any comments?

I use StGIT for my Linux patches on top of the mainline kernel and I
find it quite useful for keeping my changes in separate logical
commits (which can be updated). I'm probably not the right person to
praise it since I'm the one who wrote/maintains it :-).

Anyway, it is useful mainly for contributors that expect their patches
to be merged upstream. For the maintainer would make sense only on a
development/testing branch where patches are imported and validated
before being pushed to the stable branch.

I will make a new release this weekend with an updated README
describing its usage since the tool evolved and the documentation is a
bit outdated.

Catalin