On Mon, Apr 23, 2018 at 02:32:11PM +0100, Daniel P. Berrangé wrote:
On Mon, Apr 23, 2018 at 03:20:53PM +0200, Ján Tomko wrote:
I found the reverse order, i.e.
'rust PATCH'
to be both nicer and more useful. (not to mention more common)
For example, in some downstream lists I use a simple text ma
On Mon, Apr 23, 2018 at 03:39:13PM +0200, Andrea Bolognani wrote:
> On Mon, 2018-04-23 at 15:20 +0200, Ján Tomko wrote: > On Mon, Apr 23, 2018 at
> 01:54:32PM +0100, Daniel P. Berrangé wrote:
> > > +[gitpublishprofile "default"]
> > > +base = master
> > > +to = libvir-list@redhat.com
> > > +prefix
On Mon, 2018-04-23 at 15:20 +0200, Ján Tomko wrote: > On Mon, Apr 23, 2018 at
01:54:32PM +0100, Daniel P. Berrangé wrote:
> > +[gitpublishprofile "default"]
> > +base = master
> > +to = libvir-list@redhat.com
> > +prefix = PATCH rust
>
> I found the reverse order, i.e.
> 'rust PATCH'
> to be both
On Mon, Apr 23, 2018 at 03:20:53PM +0200, Ján Tomko wrote:
> On Mon, Apr 23, 2018 at 01:54:32PM +0100, Daniel P. Berrangé wrote:
> > The "git-publish" tool is a useful git extension for sending patch
> > series for code review. It automatically creates versioned tags
> > each time code on a branch
On Mon, Apr 23, 2018 at 01:54:32PM +0100, Daniel P. Berrangé wrote:
The "git-publish" tool is a useful git extension for sending patch
series for code review. It automatically creates versioned tags
each time code on a branch is sent, so that there is a record of
each version. It also remembers t
The "git-publish" tool is a useful git extension for sending patch
series for code review. It automatically creates versioned tags
each time code on a branch is sent, so that there is a record of
each version. It also remembers the cover letter so it does not
need re-entering each time the series i
