[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Repairing the elpa branch
From: |
Stefan Monnier |
Subject: |
Re: Repairing the elpa branch |
Date: |
Mon, 14 Jan 2013 20:44:15 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
>> And the r170 merge is not special, IIUC.
> Oh, I thought it was because it came from bzr-git, or bzr join, or
> something?
Yes (it's actually a bzr join of a bzr-git branch), but most of the
other merges do as well.
>> It was just the first such merges, so if you replace it with a flat
>> commit, the next merge will turn into the source of the problem.
> Then it seems pointless for me to try and copy the merges?
> But r10, 28, 33, 76 were also merges...
IIUC these are "normal merges" of Bzr branches of elpa (and AFAIK these
branches were very short lived and we don't need to keep track of that
merge metadata for future merges).
Stefan
- Re: Repairing the elpa branch, (continued)
- Re: Repairing the elpa branch, Stefan Monnier, 2013/01/15
- Re: Repairing the elpa branch, Stephen J. Turnbull, 2013/01/15
- Re: Repairing the elpa branch, Eli Zaretskii, 2013/01/15
- Re: Repairing the elpa branch, Glenn Morris, 2013/01/15
- Re: Repairing the elpa branch, Glenn Morris, 2013/01/15
- Re: Repairing the elpa branch, Eli Zaretskii, 2013/01/15
- Re: Repairing the elpa branch, Glenn Morris, 2013/01/15
- Re: Repairing the elpa branch, Stefan Monnier, 2013/01/15
- Re: Repairing the elpa branch, Stefan Monnier, 2013/01/15
Re: Repairing the elpa branch, Glenn Morris, 2013/01/14