Re: b4 submit ready for beta testing

["Michael S. Tsirkin" <mst@redhat.com>]

On Sun, Jul 17, 2022 at 12:02:18PM -0400, Konstantin Ryabitsev wrote:
> On Sat, Jul 16, 2022 at 12:55:26PM -0400, James Bottomley wrote:
> > >  So, if you work on a series, send it off, and then pick it up again
> > > two weeks later from a different workstation, that's no good for most
> > > of what b4 submit needs to do. :(
> > 
> > Are you so sure that's the common case.  For me, to connect to an SMTP
> > server, I need to be on a system running my VPN, which is only my
> > laptop.  Thus however much I transfer the series around for testing
> > etc., it always comes back to the same system for submission, so
> > keeping the cover letter in the branch description of that system works
> > just fine.
> 
> Perhaps, but I also have other reasons to like using an empty commit for this.
> For example, it makes it very easy to mark where exactly our series starts.
> It's possible to do this with other tricks like tracking merge-base, using
> tags, etc, but they are a lot more complicated and have other caveats (e.g.
> when using merge-base tricks you have to also track the branch you forked
> from, and when using tags you have to also consider that someone may push the
> branch but not push the tags).

Very much this. Further, I hope down the road it will become possible
to keep serveral series stacked on top of each other.

-- 
MST