From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from astoria.ccjclearline.com ([64.235.106.9]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1X0UjW-0006kl-PG for barebox@lists.infradead.org; Fri, 27 Jun 2014 11:54:23 +0000 Date: Fri, 27 Jun 2014 07:49:49 -0400 (EDT) From: "Robert P. J. Day" In-Reply-To: Message-ID: References: <20140627045150.GN14257@pengutronix.de> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: where is Documentation/parameters.txt? To: Holger Schurig Cc: "U-Boot Version 2 (barebox)" On Fri, 27 Jun 2014, Holger Schurig wrote: > > oh, sorry, i missed that doc *branch*, my fault. > > It's totally new ... and awesome (compared to the old docs). ok, possibly a silly question but, as i now read it, if i want to work with the sphinx-based docs, i should be working off the "doc" branch and restrict my changes to just the files in the Documentation directory. but recently, i submitted a patch to correct the misspelling "persistant", and some of those changes were in Documentation/, while other examples of that were scattered elsewhere (arch/, scripts/). so what's the protocol for correcting "documentation" (eg., inline comments in source files) as opposed to the content under Documentation? should non-Documentation patches be submitted against the master branch? or does the "doc" branch track master closely enough that i can exclusively stay on the "doc" branch? as in, should i resubmit that earlier patch broken into two parts? and if one submits a patch against the "doc" branch, should that be identified in the patch itself? the subject line? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox