Ticket #71 (closed enhancement: fixed)
generate "specific" SourceStamps from "HEAD" ones
| Reported by: | dustin | Owned by: | warner |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.7.7 |
| Version: | 0.7.5 | Keywords: | |
| Cc: |
Description
Patch to allow SourceStamps? to be updated from an "original" SourceStamp? (based on a set of Changes) to a "specific" SourceStamp? (with an explicit revision). Default functionality of BuildStatus?.getSourceStamp() is not altered.
This patch should be applied after #70
Attachments
Change History
comment:1 Changed 6 years ago by warner
- Priority changed from major to minor
- Status changed from new to assigned
- Version set to 0.7.5
- Milestone changed from undecided to 0.7.6
Ahh.. that's what you meant by "specific".. got it.
I like the idea, let me think about the terminology for a little while before applying this one.
comment:2 Changed 6 years ago by dustin
Yeah, I'm totally happy to be overridden on the terminology :)
comment:4 Changed 6 years ago by warner
- Summary changed from update SourceStamps to generate "specific" SourceStamps from "HEAD" ones
comment:5 Changed 5 years ago by warner
- Milestone changed from 0.7.7 to 0.7.8
no progress on this yet, bumping to 0.7.8
comment:6 Changed 5 years ago by dustin
how about "canonical SourceStamps?"?
"HEAD" is really a relative term -- its meaning changes depending on time. We could also call the revision-specific SourceStamps? "absolute SourceStamps?"
comment:7 Changed 5 years ago by dustin
- Milestone changed from 0.7.8 to 0.7.7
Updated version. Brian, unless there are objections, please pull the patch of this name from http://darcs.r.igoro.us/buildbot/trunk. This sort of thing has been requested a few times on the mailing list.
comment:8 Changed 5 years ago by dustin
- Status changed from assigned to new
#71:absolute-sourcestamps.patch in http://darcs.r.igoro.us/buildbot/dustin/
![[Buildbot Logo]](/chrome/site/header-text-transparent.png)
