Re: Git, where zombie branches shamble again

2021-11-16 Thread Dave Kemper
On 11/1/21, G. Branden Robinson wrote: > or until we can devise > some contributor-facing documentation that tells us all what is expected > and how to perform routine tasks like branch creation, management > (without blitzing the -commit list), and deletion. I have no stake in this, as I'm not r

Re: Git, where zombie branches shamble again

2021-11-02 Thread Larry McVoy
On Tue, Nov 02, 2021 at 07:20:03AM +, Werner LEMBERG wrote: > > >> You absolutely _did_ rewrite history ... not just once, but twice! > >> You deleted an _entire branch_ of published development history, > >> then after my subsequent push had reinstated it, you deleted it > >> once again! If

Re: Git, where zombie branches shamble again

2021-11-02 Thread Werner LEMBERG
>> You absolutely _did_ rewrite history ... not just once, but twice! >> You deleted an _entire branch_ of published development history, >> then after my subsequent push had reinstated it, you deleted it >> once again! If that isn't rewriting history, then I'd like to know >> what you would call

Re: Git, where zombie branches shamble again

2021-11-01 Thread G. Branden Robinson
At 2021-11-01T22:30:28+, Keith Marshall via Groff-commit wrote: > On 01/11/2021 14:01, G. Branden Robinson wrote: > > At 2021-10-24T18:53:52-0700, Larry McVoy wrote: > >> On Mon, Oct 25, 2021 at 11:58:55AM +1100, G. Branden Robinson > >> wrote: > >>> Since I am now accused four times over of re

Re: Git, where zombie branches shamble again

2021-11-01 Thread Keith Marshall
On 01/11/2021 14:01, G. Branden Robinson wrote: > At 2021-10-24T18:53:52-0700, Larry McVoy wrote: >> On Mon, Oct 25, 2021 at 11:58:55AM +1100, G. Branden Robinson wrote: >>> Since I am now accused four times over of rewriting history, and >>> moreover of violating an "absolute taboo", I must insist

Re: Git, where zombie branches shamble again

2021-11-01 Thread G. Branden Robinson
Hi, Larry! At 2021-10-24T18:53:52-0700, Larry McVoy wrote: > On Mon, Oct 25, 2021 at 11:58:55AM +1100, G. Branden Robinson wrote: > > Since I am now accused four times over of rewriting history, and > > moreover of violating an "absolute taboo", I must insist upon the > > presentation of particula

Re: Git, where zombie branches shamble again

2021-10-24 Thread Larry McVoy
On Mon, Oct 25, 2021 at 11:58:55AM +1100, G. Branden Robinson wrote: > > +1 except in extraordinary circumstances. > > Since I am now accused four times over of rewriting history, and > moreover of violating an "absolute taboo", I must insist upon the > presentation of particulars. Hi, I'm the Bi

Re: Git, where zombie branches shamble again

2021-10-24 Thread G. Branden Robinson
I had a longer response to this, but it's probably better to cut to the chase. First I'll quote the charge sheet. At 2021-10-24T20:35:44+0100, Keith Marshall wrote: > to push the first change in my local patch queue ... and incidentally, > (and unexpectedly), restore the public repository history

Re: Git, where zombie branches shamble again

2021-10-24 Thread Larry McVoy
On Sun, Oct 24, 2021 at 08:35:44PM +0100, Keith Marshall wrote: > What you describe may be a manifest *effect* of the problem; the *real* > problem is that, contrary to established wisdom, you've abused git's > ability to rewrite history, within a public repository ??? that should be > an absolute

Re: Git, where zombie branches shamble again

2021-10-24 Thread Keith Marshall
On 24/10/2021 03:16, G. Branden Robinson wrote: > [Here's another long email; Ralph may want to skip it.] > At 2021-10-23T22:07:27+0100, Keith Marshall via Groff-commit wrote: >> Well, I pulled, and updated my local tree, to capture Brandon's most >> recent commits, then applied _one_ trivial ms pa

Git, where zombie branches shamble again

2021-10-23 Thread G. Branden Robinson
[Here's another long email; Ralph may want to skip it.] Hi Keith, At 2021-10-23T22:07:27+0100, Keith Marshall via Groff-commit wrote: > Guys, > > I have no idea what's happened here! [...] > Well, I pulled, and updated my local tree, to capture Brandon's most > recent commits, then applied _one_