[PATCH 0 of 8] Interraction between obsolete changesets and exchange operation

Pierre-Yves David pierre-yves.david at logilab.fr
Fri Jul 6 12:22:24 CDT 2012


On Fri, Jul 06, 2012 at 12:06:00PM +0300, Idan Kamara wrote:
> On Fri, Jul 6, 2012 at 3:27 AM, Pierre-Yves David <
> pierre-yves.david at ens-lyon.org> wrote:
> >
> > This series implement basic filtering of obsolete changeset during
> > exchange
> > operation.
> >
> > It's based on the "not that good" implementation of secret changeset
> > filtering.
> > The righ way to do that would be to implement changelog level filtering
> > but we
> > are too late in the release cycle for that. In the other hand such
> > filtering is
> > too much central to the obsolete concept to be delayed.
> 
> Is anything going to use obsolete before 2.4? If not, what's the rush
> of adding these things the wrong way?

hehe, switching role :-)

Filtering of obsolete changeset is a very core concept of obsolete and
virtually no use of obsolete marker can be done without it.

My initial idea was to keep quick and dirty filtering in my extension and to
add real life creator of obsolete marker.  But Matt do prefer to have some of
the behavior changes of obsolete before adding any creator. So I'm trying to
move as much behavior feature of my obsolete extension into core before the
freeze.

If exchange and display filtering get into core quickly enought. patching
--amend, rebase and histedit to create obsolete marker is trivial or already
solved in my extension.

In all case my evolve extension will be able to create and use obsolete marker
and anything moved into 2.3 is a net benefit for it.

--

Note: I'm not adding new wrong way to do that. I'm extending existing wrong way.

Second Note: The good side is that we'll have more existing testcase for changelog level filtering.


-- 
Pierre-Yves David

http://www.logilab.fr/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20120706/05fd4ffa/attachment.pgp>


More information about the Mercurial-devel mailing list