Re: do not propogate a changeset
Konstantin Osipov <[email protected]>
| Newsgroups | gmane.comp.version-control.bitkeeper.user |
|---|---|
| Message-ID | <[email protected]> |
* Wayne Scott <[email protected]> [04/10/13 17:38]: > > The two trees above need to have different post-commit triggers. > > Is it possible to do? > If we are just talking about triggers I can think of two options: > > - Just don't check in the triggers. > > The triggers don't need to be committed to the BitKeeper repository. > They can just be setting in the triggers directory. > > - Make one script that performs both functions and just switches > based on the current hostname, pathname or repo_id. Actually it's a bit more complicated, all commits are performed into clones: 4.1 < -- > 4.1-ndb / \ / \ 4.1-kostja 4.1-sanja .. 4.1-ndb-pekka 4.1-ndb-tomas .. We're considering the second approach, but thinking of using bk parent to distinguish between these two branches. Thanks! -kostja _______________________________________________ Bitkeeper-users mailing list [email protected] http://bitmover.com/mailman/listinfo/bitkeeper-users To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.