[OpenWalnut-Dev] [Discussion] New Commit Tag and Rule
Sebastian Eichelbaum
eichelbaum at informatik.uni-leipzig.de
Tue Aug 17 11:34:01 CEST 2010
On Tue, 17 Aug 2010, Alexander Wiebel wrote:
>
> > [PATCH] - injected feature_1 and style_changes from branch
> > 2333:fda591666g23
> Accepted from my side.
Accepted too
>
> > Also I propose to use the [MERGE] tag (and actually doing also a real
> > merge) when transferring a whole changeset over branches.
> Does not always do what [PATCH] is meant to do.
>
> > Thinking this will make the [---] Tag obsolete.
> Yup.
>
> > Also I recommend to not
> > just put the checksum of the revision into the commit messages but also
> > the ID, _knowing_ that they may differ on every repo, but they give you a
> > glimpse where to find the revision in hgview (used by some of us, and
> > sorts the revisions by ID). Sure you may do a:
>
> I find it confusing to use the revision numbers. I would suggest to got to the
> code browser of the trac. There all the checksums are links.
The revision number is a bad idea. You simply can't use it as most would intend. Ok, it gives you a clue. But lets summarize the situations where you see such a number:
* reading commit emails
- there you do not need the revision number as the date/time of the mail is sufficient
- besides this, you do not read commit emails from last year, aren't you?
* reading trac
- click on it
* browsing using hgview
- you visually see from where with what it was merged
Sebastian
>
>
> Alex
> _______________________________________________
> OpenWalnut-Dev mailing list
> OpenWalnut-Dev at lists.informatik.uni-leipzig.de
> http://lists.informatik.uni-leipzig.de/mailman/listinfo/openwalnut-dev
>
--
Dipl.-Inf. Sebastian Eichelbaum
Universität Leipzig
Institut für Informatik
Abteilung Bild- und Signalverarbeitung
PF 100920
D-04009 Leipzig
More information about the OpenWalnut-Dev
mailing list