freeipmi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freeipmi-devel] Re: single tree


From: Anand Babu
Subject: Re: [Freeipmi-devel] Re: single tree
Date: Thu, 06 May 2004 07:19:32 -0700
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

,----[ Albert Chu <address@hidden> ]
| > In theory, we can still create a new subdirectory src and remove the
| > other 2.  Depends how strongly teammates feel about it.
| 
| Personally, I'd rather do this.  I know right off the bat that the
| root project directory is going to get cluttered with a lot of
| 
| DISCLAIMER.ipmipower DISCLAIMER.ipmiping DISCLAIMER.rmcpping
| DISCLAIMER.bmc-watchdog
| 
| and other stuff really fast.
`----

It is OK to have such files on the top level directory. It is also
possible to group such files and place them in appropriate sub
directories, like dist or bla-bla.

One advantage of having Ian's model is, it clearly segregates
sub-trees, like 'extensions', 'scripts' under 'fish' instead of
top-level 'freeipmi'.

I like the current tree structure too. If others don't object, let us
live with this model. 

,----[ Albert Chu <address@hidden> ]
| > The reason for my preference is that otherwise you have to enter the
| > same information twice (once for CVS, once for ChangeLog).  Myself,
| > I can never remember to do that, or if I do, I can't remember to
| > copy the string so I can later paste it in the other spot.
| 
| AB, Bala, could you throw in votes??
`----

Changelog is places an important role in developers communication. 
CVS logs doesn't convey enough all the time. Lot of times, It is
impossible to describe multiple changes with cvs -m argument on a
single commit.

I vote for manual Changelog.

-- 
Anand Babu
Free as in Freedom <www.gnu.org>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]