On 21 September 2010 22:15, Timothy Brownawell wrote:
> Do you want to push all/most of your company's changes upstream, or only
> specific changes you can identify in advance, or randomly-chosen changes?
> Does work generally *need* to be accepted upstream, or can you identify
> specific things y
Timothy Brownawell writes:
> On 09/20/2010 02:05 AM, Stephen Leake wrote:
>> One request: you committed one revision that is both a propagate, and
>> has other changes:
>>
>> 8434d5524dde039f70c7ff347b5de32cf7b9043b
>> 2010-09-19T21:03:25 Timothy Brownawell
>> Merge in changes and
On 09/20/2010 07:23 PM, Brian May wrote:
Hello,
I asked a similar question on my local mailing list concerning git.
Just wondered what perspective I would get here, in particular with
monotone people. I think similar issues apply in both cases.
Lets say I am tracking an upstream project. As I a
On 09/21/2010 03:15 AM, Thomas Keller wrote:
Instead of disapproving J with K one could also try to suspend J and
branch off on one of its parents. I have to admit though that I'm unsure
if monotone keeps the suspended branch and its revision(s) in your local
database only or if they would be tra
Am 21.09.2010 02:23, schrieb Brian May:
> Hello,
>
> I asked a similar question on my local mailing list concerning git.
> Just wondered what perspective I would get here, in particular with
> monotone people. I think similar issues apply in both cases.
>
> Lets say I am tracking an upstream proj
