On Fri, Sep 12, 2008 at 7:11 PM, Colin Watson <email address hidden> wrote:
> John, when you say that 1) "won't propagate", does that mean that
> existing branches will be broken and everyone will have to re-clone from
> scratch? (Not that there are all that many existing branches since the
> breakage has made it difficult for people to branch.)
No, he means that if someone pulls or merges from one of the branches
with this inserted, the puller won't automatically get the fix.
(This is because we're going back to insert a revision that's kind of
half-present and the code to determine what to fetch doesn't search
through things that should already be present.)
So people affected by this would need to either run the command to fix
it, or re-clone.
On Fri, Sep 12, 2008 at 7:11 PM, Colin Watson <email address hidden> wrote:
> John, when you say that 1) "won't propagate", does that mean that
> existing branches will be broken and everyone will have to re-clone from
> scratch? (Not that there are all that many existing branches since the
> breakage has made it difficult for people to branch.)
No, he means that if someone pulls or merges from one of the branches
with this inserted, the puller won't automatically get the fix.
(This is because we're going back to insert a revision that's kind of
half-present and the code to determine what to fetch doesn't search
through things that should already be present.)
So people affected by this would need to either run the command to fix
it, or re-clone.
-- launchpad. net/~mbp/>
Martin <http://