[isabelle-dev] Odd branches on AFP

[Gerwin Klein]

Thanks for closing that branch again.

As Salomon explained it was accidental, but just in case there was unclarity about it for others: the afp development model is to not use mercurial internal branches, but forks and repository merges instead.

Perfectly fine to use branches in your own copy of course if that’s what you want to do, but we would not want to create multiple branches inside the main afp-devel repository on bitbucket.

To answer Makarius’ question, there is a use case for named branches: when you want to record in history which commits belonged to which branch (for instance a feature branch), and how those branches developed over time. It’s not something we need for the AFP or Isabelle, but if you have something like a feature branch workflow, it does occasionally come in handy.

Cheers,
Gerwin



> On 30.03.2016, at 20:50, Makarius <makarius at sketis.net> wrote:
>
> On Wed, 30 Mar 2016, Salomon Sickert wrote:
>
>> Apparently SourceTree pushed all my local branches instead of the selected commits.
>
> I've heard of SourceTree, but have not tried it yet. Is it worth spending time on it?
>
> From a distance, I would expect that local development is done with Mercurial queues, not branches.  For me the question remains open, if Mercurial branches have any purpose at all. Nobody could explain this to me.
>
>
>       Makarius
>
> _______________________________________________
> isabelle-dev mailing list
> isabelle-dev at in.tum.de
> https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev


________________________________

The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.