We currently have
- documentation/cbfs.txt - util/cbfstool/README (almost exact copy of the above) - http://www.coreboot.org/CBFS (wikified copy of the above).
Attached patch drops the two text files in favor for the wiki page, which is a lot easier to keep up-to-date.
Uwe.
On Fri, 9 Oct 2009 17:49:18 +0200, Uwe Hermann uwe@hermann-uwe.de wrote:
We currently have
- documentation/cbfs.txt
- util/cbfstool/README (almost exact copy of the above)
- http://www.coreboot.org/CBFS (wikified copy of the above).
Attached patch drops the two text files in favor for the wiki page, which is a lot easier to keep up-to-date.
Maybe just a quick readme pointing the wiki page for complete documentation?
On 09.10.2009 17:55, Joseph Smith wrote:
On Fri, 9 Oct 2009 17:49:18 +0200, Uwe Hermann uwe@hermann-uwe.de wrote:
We currently have
- documentation/cbfs.txt
- util/cbfstool/README (almost exact copy of the above)
- http://www.coreboot.org/CBFS (wikified copy of the above).
Attached patch drops the two text files in favor for the wiki page, which is a lot easier to keep up-to-date.
Maybe just a quick readme pointing the wiki page for complete documentation?
Can we please leave one in-tree copy intact? I am regularly working on my tree when I don't have a net connection.
Regards, Carl-Daniel
On Fri, Oct 09, 2009 at 06:08:16PM +0200, Carl-Daniel Hailfinger wrote:
Maybe just a quick readme pointing the wiki page for complete documentation?
Can we please leave one in-tree copy intact? I am regularly working on my tree when I don't have a net connection.
Dunno, I too work offline a lot, but it's not like we edit cbfs.txt on a daily basis. I want to avoid duplicate versions, as they will surely diverge over time and confuse folks which of them to edit etc.
Uwe.
On 10.10.2009 17:17, Uwe Hermann wrote:
On Fri, Oct 09, 2009 at 06:08:16PM +0200, Carl-Daniel Hailfinger wrote:
Can we please leave one in-tree copy intact? I am regularly working on my tree when I don't have a net connection.
Dunno, I too work offline a lot, but it's not like we edit cbfs.txt on a daily basis. I want to avoid duplicate versions, as they will surely diverge over time and confuse folks which of them to edit etc.
Can't we copy the flashrom model where the master is in the repo and the wiki gets a tag "do not change manually" and regular updates from the repo? Hey, you can even have the wiki point to the permanently checked out source in trac. No duplication at all that way.
Regards, Carl-Daniel
On Sat, Oct 10, 2009 at 05:32:42PM +0200, Carl-Daniel Hailfinger wrote:
On 10.10.2009 17:17, Uwe Hermann wrote:
On Fri, Oct 09, 2009 at 06:08:16PM +0200, Carl-Daniel Hailfinger wrote:
Can we please leave one in-tree copy intact? I am regularly working on my tree when I don't have a net connection.
Dunno, I too work offline a lot, but it's not like we edit cbfs.txt on a daily basis. I want to avoid duplicate versions, as they will surely diverge over time and confuse folks which of them to edit etc.
Can't we copy the flashrom model where the master is in the repo and the wiki gets a tag "do not change manually" and regular updates from the repo? Hey, you can even have the wiki point to the permanently checked out source in trac. No duplication at all that way.
OK then, let's kill util/cbfstool/README and make the wiki page point to the trac file.
Will commit/fix in the evening, unless somebody onjects.
Uwe.
On Fri, Oct 16, 2009 at 04:15:09PM +0200, Uwe Hermann wrote:
OK then, let's kill util/cbfstool/README and make the wiki page point to the trac file.
Will commit/fix in the evening, unless somebody onjects.
Done.
Uwe.
-
Carl-Daniel Hailfinger -
Joseph Smith -
Uwe Hermann