Invalid time stamp in last upload
joerg at alea.gnuu.de
Sun Feb 15 17:59:38 UTC 2009
Rafael Laboissiere hat am Sat 14. Feb, 22:41 (+0100) geschrieben:
> * Jörg Sommer <joerg at alea.gnuu.de> [2009-02-14 15:13]:
> > Rafael Laboissiere hat am Sat 14. Feb, 13:53 (+0100) geschrieben:
> > > * Jörg Sommer <joerg at alea.gnuu.de> [2009-02-14 12:46]:
> > >
> > > > Muck, you've forgot to update the time stamp.
> > >
> > > Argh! I have overseen that.
> That happened because we have different work styles. In the other
> collaborative packaging projects I am involved, we always have a sane
> trailer line in SCM, such that uploaders can do the release straight away
> from the repository. You once raised the objection that the trailer line
> should not be changed before the actual release in order to avoid polution
> of the changesets.
Yes, pollution, because the information when this change was made is
recorded by the VCS. But the biggest problem I see is merging, rebasing
and cherry-picking. On the dpkg mailinglist, a discussion about changelog
enties is ongoing “GNU ChangeLogs, commit logs and commits,” where
Guillem named the changelog files as the biggest source of conflicts.
If you change with each update the timestamp this line differs in all
commits. Due to this you will get a conflict everytime you move commits
But I assume you don't do any commit movements in the other project or
what's your experience regarding commit movements?
Der Wille und nicht die Gabe macht den Geber.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: Digital signature http://en.wikipedia.org/wiki/OpenPGP
Url : http://lists.alioth.debian.org/pipermail/pkg-jed-devel/attachments/20090215/d6e4dee0/attachment.pgp
More information about the Pkg-jed-devel