On 6 May 2014 13:58, Noon Silk <[email protected]> wrote: > On Tue, May 6, 2014 at 1:46 PM, Javier Candeira <[email protected]> wrote: >> >> The changes are contained in a git commit, so you can put that in your >> requirements.txt and ask everyone to update (or have the update in a >> git hook). > > > But how do they get the commit? To which repo did it go? Ah, I see, in your > scenario here the commit is going to your own fork of the main project. > Alright. I guess in order to make this work each developer needs to have a > fork of the common repo, but if you do this, it avoids the situation I > describe below.
Often each project has its own fork of the repos it depends on. There shouldn't really be any difference between these and upstream, but if there needs to be, there is enough indirection for you to do so. If you maintain the project, it could just be a branch or tag rather than a separate repo. -- William Leslie Notice: Likely much of this email is, by the nature of copyright, covered under copyright law. You absolutely MAY reproduce any part of it in accordance with the copyright law of the nation you are reading this in. Any attempt to DENY YOU THOSE RIGHTS would be illegal without prior contractual agreement. _______________________________________________ melbourne-pug mailing list [email protected] https://mail.python.org/mailman/listinfo/melbourne-pug
