On Monday 13 March 2006 10:37, Stefan Küng wrote:
> On 3/13/06, Lübbe Onken <l.onken@rac.de> wrote:
> > Tobias Schäfer wrote:
> > > At my company we are currently generate a Changelog.txt file
> > > daily and commit
> > > it to the repository.
> >
> > I like that idea. How about taking that approach as well? We could either
> > limit the daily changelog to a certain start revision like Stefan did or
> > we could limit the changelog to the last N revisions on a path (e.g.
> > trunk.
> >
> > I'd just love to be able to look at:
> > http://tortoisesvn.tigris.org/svn/tortoisesvn/branches/1.3.x/changelog.ht
> >ml
> > http://tortoisesvn.tigris.org/svn/tortoisesvn/branches/1.2.x/changelog.ht
> >ml http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/changelog.html
>
> "Repository Browser"->"Show Log", and you have the information you want.
>
> That's an invitation for conflicts to happen. While the idea has its
> pros, I don't like to have generated files in our sourcetree (I even
> don't like the generated pot files).
We have the usual /trunk /tags and /branches repository structure and the
Changelog-File is at /ChangeLog.txt. Having it outside of those directories
assures that It cannot cause conflicts when branching and merging. Besides
that the build machine always does an svn-update, deletes the file, creates
the file and then commits it. The only way to cause a conflict is to get up
at 05:00 in the morning and commit a file in the short time span between the
update und commit of the build machine :-)
It all boils down to the question if you want to have generated files in the
repository. For TSVN I don't see the benefit.
Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Mar 13 19:39:41 2006