Date: Mon, 03 Jun 2013 16:40:59 +0200 From: Gabor Kovesdan <gabor@FreeBSD.org> To: Tom Rhodes <trhodes@FreeBSD.org> Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org, dru.lavigne@att.net Subject: Re: svn commit: r41824 - head/en_US.ISO8859-1/books/handbook Message-ID: <51ACAAFB.1070807@FreeBSD.org> In-Reply-To: <20130603102747.44431f4a.trhodes@FreeBSD.org> References: <1370264382.6045.YahooMailClassic@web184906.mail.gq1.yahoo.com> <51AC956D.1040405@FreeBSD.org> <20130603102747.44431f4a.trhodes@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Em 03-06-2013 16:27, Tom Rhodes escreveu: > This sounds really cool, I think we should have a discussion > on how to do this, if we want to do this, and how we could > go about using only one version. Personally, I kind of like > a development version where we can make changes, discuss them, > fix them, as a team, and have them slowly merged into a version > that will appear on the web.:) I see that point but I think most changes are trivially demanded, e.g. style and grammar improvement, elimination of you, etc. These could directly go to head. On the other hand, reorganization of chapters is something that needs care and discussion so it could happen in a separate branch. But reducing the number of changes in that branch and not mixing mergeable and not mergeable changes can significantly facilitate the process. The questions is now if it is desired to go back to one development line again. If so, we need a list of changes that cannot directly be merged from the ISBN branch, solve them there to use a single source solution and then merge back the whole branch and continue in head. Gabor
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51ACAAFB.1070807>