Advocacy vs. git

[Hans Meine]

On Tuesday 28 April 2009 01:33:17 Martin Geisler wrote:
> The histedit extension allows you to quickly decide on the fate of a
> bunch of changesets by editing a text file in your editor. You make some
> commits
>
>   [a] --- [b] --- [c] --- [d]
>
> and then decide to rework changesets b, c, and d:
>
>   hg histedit b
>
> This drops you into your editor with a file that looks like this:
>
>   pick 655c435efe92 b
>   pick c47d17a27e19 c
>   pick b04d79f9e2dd d

Thanks.  That's very useful as a start, and Augie's README was very 
informative, too.  I'll try it out now.

> See also the tests here:
>
>   http://bitbucket.org/durin42/histedit/src/tip/tests/

Actually, I *did* look at them (in the absence of any docs), but it's hard to 
understand them without knowing the context (stuff being shown in an editor 
etc.).

Looks like histedit could become really useful.

It would be great if there was a way to keep track of "shared" changesets, 
i.e. ones that I were already pushed or cloned, such that editing them should 
be prohibited (or warned about).  AFAICS it's not safely possible (in 
particular, anyone with a local login can clone my world-readable repo without 
me knowing it), but when everyone pushes/pulls to/from a shared central repo, 
it might be feasible (and useful).

Have a nice day,
  Hans