[hipl-dev] Re: [Branch ~hipl-core/hipl/trunk] Rev 6282: Rename function hip_close to hipd_close
- From: Diego Biurrun <diego@xxxxxxxxxx>
- To: hipl-dev@xxxxxxxxxxxxx
- Date: Thu, 16 Feb 2012 12:23:51 +0100
On Wed, Feb 15, 2012 at 05:13:40PM +0200, Miika Komu wrote:
> On 02/15/2012 03:10 PM, Xin Gu wrote:
> >On 15/02/12 14:55, David Martin wrote:
> >>On Wed, Feb 15, 2012 at 1:25 PM, Xin Gu<eric.nevup@xxxxxxxxx> wrote:
> >>
> >>>I realize that since I will change the prefix of new API in
> >>>libhip branch to "hipl_", current modification in trunk becomes
> >>>meaningless. So I will just uncommit it.
> >>Oh. You should never ever mess with the history on public branches /
> >>branches that are not your own! If you remove commits from somewhere
> >>in the middle of the history it looses its consistency across the
> >>different branches people have checked out and all hell breaks loose.
> >>So for the future, never uncommit or push with --overwrite on trunk.
> >>:)
> >>
> >>(Diego probably is crying tears of joy right now)
> >>
> >Hmm, sorry for that, I thought in this situation it might be acceptable,
> >will be careful next time.
>
> we need to document the right way to revert to HACKING.
Looks like an exercise in futility to me. As we have plainly seen, new
people do not read it and/or are not advised to read it.
There's two paragraphs of memorable prose in HACKING describing why not
to mess with uncommit on public branches. If that does not work, the
only alternative I see are either actually insulting people in big fat
SHOUTING ALL CAPS THAT WARN OF DIRE STRAITS TO TRESPASSERS or simply not
letting newbies commit directly.
The latter sounds like the way to go. Obviously handing people a sharp
knife and an instruction manual only results in tears and accidents.
Let's give them a dummy knife first and only upgrade to the sharp variant
once they have proven basic knife handling skills.
Diego
Other related posts:
