|
Boost : |
Subject: Re: [boost] git reset and force push
From: Daniel James (dnljms_at_[hidden])
Date: 2015-10-07 17:35:11
On 7 October 2015 at 08:25, Raffi Enficiaud
<raffi.enficiaud_at_[hidden]> wrote:
>
> Ok, this is what I wanted to know. Basically I recreated a develop branch
> for boost.test release to develop (then to master) on a clean history. I
> wanted to know if the git bot of the modular boost (the one that commits
> under the name "Automated Commit <automated_at_[hidden]>") is able to
> take just the sha of the develop branch, or if its relying on some linear
> history.
I'm the maintainer of the bot, so I'll add a quick reply. It just
reads new commit hashes from the github api, and pays no attention to
module history so it has no problems with force pushes. But that
doesn't mean they're okay, they can cause all sorts of problems for
people who have branches, for the history of the super-project, for
scripts which assume a linear history, and for developers who aren't
fully versed in git techniques. I haven't read all of the thread, but
it looks like this has all been discussed.
Also, if you have any further questions about the bot, please make it
clear in the subject, so that it will get my attention. I don't read
most threads.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk