[Maxima-commits] [git] Maxima CAS branch, parse-info, deleted. branch-5_30-base-22-gb657f3b



Raymond Toy <toy.raymond at gmail.com> writes:
> On 4/4/13 8:02 AM, Rupert Swarbrick wrote:
>> This is an automated email from the git hooks/post-receive script. It was
>> generated because a ref change was pushed to the repository containing
>> the project "Maxima CAS".
>>
>> The branch, parse-info has been deleted
>>        was  b657f3bdc262bf14906f792a8608eb2947a45aa4
>>
> I'm just a git user, and I could be wrong, but I think it's generally a
> bad idea to delete an upstream branch and then recreate a new branch
> with the same name.  It certainly messed up my local branch a bit which
> was current but then suddenly was 50 some commits ahead of the
> origin/parse-info branch.
>
> The easiest solution for me was to just remove my local branch and get a
> new copy.
>
> (And can we have better branch names than bs2?)

Yes, and yes.

Sorry about the deletion: I assumed that no-one was tracking the
non-master branches and that it made more sense to rebase them like
this. Now I've seen that it's annoying someone, I'll do a proper merge
next time.

Rupert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 315 bytes
Desc: not available
URL: <http://www.math.utexas.edu/pipermail/maxima/attachments/20130408/d7af44b5/attachment.pgp>;