[PATCH v2] git-publish: add profile

[PATCH v2] git-publish: add profile

[Matias Ezequiel Vara Larsen]

Add git-publish profile and document how to use it.

Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
---
v1 -> v2: 
   * add link to git-publish
   * document that the project contain a profile already
---
 .gitpublish |  3 +++
 README.md   | 13 +++++++++++++
 2 files changed, 16 insertions(+)
 create mode 100644 .gitpublish

diff --git a/.gitpublish b/.gitpublish
new file mode 100644
index 0000000..d412896
--- /dev/null
+++ b/.gitpublish
@@ -0,0 +1,3 @@
+[gitpublishprofile "default"]
+base = master
+to = virtio-comment@lists.linux.dev
diff --git a/README.md b/README.md
index c06caf6..3df3fb2 100644
--- a/README.md
+++ b/README.md
@@ -110,6 +110,19 @@ git format-patch -o proposal1/ HEAD~1..<br>
 git send-email --to=virtio-comment@lists.linux.dev proposal1/0001-*
 </code>
 
+<dl>Optionally, you can use
+<A
+HREF="https://github.com/stefanha/git-publish">git-publish</A> to submit a patch. This project already contains a git-publish's profile that will configure some fields, i.e., To field with the right address. After you have installed git-publish, the procedure is the following:
+
+<code>
+<p>
+git checkout master -b my-feature<br>
+# work on new commits, add your 'Signed-off-by' lines to each<br>
+git publish<br>
+# more work, rebase on master, ...<br>
+git publish # will send a v2<br>
+</code>
+</dl>
 <dl>
 <dt>When to use the virtio-comment mailing list:</dt>
 <dd>
-- 
2.42.0

Re: [PATCH v2] git-publish: add profile

[Albert Esteve]

On Wed, Mar 5, 2025 at 11:58 AM Matias Ezequiel Vara Larsen
<mvaralar@redhat.com> wrote:
>
> Add git-publish profile and document how to use it.
>
> Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
> ---
> v1 -> v2:
>    * add link to git-publish
>    * document that the project contain a profile already
> ---
>  .gitpublish |  3 +++
>  README.md   | 13 +++++++++++++
>  2 files changed, 16 insertions(+)
>  create mode 100644 .gitpublish
>
> diff --git a/.gitpublish b/.gitpublish
> new file mode 100644
> index 0000000..d412896
> --- /dev/null
> +++ b/.gitpublish
> @@ -0,0 +1,3 @@
> +[gitpublishprofile "default"]
> +base = master
> +to = virtio-comment@lists.linux.dev
> diff --git a/README.md b/README.md
> index c06caf6..3df3fb2 100644
> --- a/README.md
> +++ b/README.md
> @@ -110,6 +110,19 @@ git format-patch -o proposal1/ HEAD~1..<br>
>  git send-email --to=virtio-comment@lists.linux.dev proposal1/0001-*
>  </code>
>
> +<dl>Optionally, you can use
> +<A
> +HREF="https://github.com/stefanha/git-publish">git-publish</A> to submit a patch. This project already contains a git-publish's profile that will configure some fields, i.e., To field with the right address. After you have installed git-publish, the procedure is the following:

Nit: remove uppercase and the line split? Also, you could use acute
accents surrounding the `To` field, to highlight it in the markdown.
Also, not sure that the genitive is correct there for `git-publish's
pofile`. And if you want to give an example, better use `e.g.` instead
of `i.e.`. So all in all, something like this maybe?

<a href="https://github.com/stefanha/git-publish">git-publish</a> to
submit a patch. This project already contains a `git-publish` profile
that will configure some fields, e.g., `To` field with the right
address. After you have installed `git-publish`, the procedure is the
following:

> +
> +<code>
> +<p>
> +git checkout master -b my-feature<br>
> +# work on new commits, add your 'Signed-off-by' lines to each<br>
> +git publish<br>
> +# more work, rebase on master, ...<br>
> +git publish # will send a v2<br>
> +</code>
> +</dl>
>  <dl>
>  <dt>When to use the virtio-comment mailing list:</dt>
>  <dd>
> --
> 2.42.0
>

Re: [PATCH v2] git-publish: add profile

[Matias Ezequiel Vara Larsen]

On Wed, Mar 05, 2025 at 02:43:05PM +0100, Albert Esteve wrote:
> On Wed, Mar 5, 2025 at 11:58 AM Matias Ezequiel Vara Larsen
> <mvaralar@redhat.com> wrote:
> >
> > Add git-publish profile and document how to use it.
> >
> > Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
> > ---
> > v1 -> v2:
> >    * add link to git-publish
> >    * document that the project contain a profile already
> > ---
> >  .gitpublish |  3 +++
> >  README.md   | 13 +++++++++++++
> >  2 files changed, 16 insertions(+)
> >  create mode 100644 .gitpublish
> >
> > diff --git a/.gitpublish b/.gitpublish
> > new file mode 100644
> > index 0000000..d412896
> > --- /dev/null
> > +++ b/.gitpublish
> > @@ -0,0 +1,3 @@
> > +[gitpublishprofile "default"]
> > +base = master
> > +to = virtio-comment@lists.linux.dev
> > diff --git a/README.md b/README.md
> > index c06caf6..3df3fb2 100644
> > --- a/README.md
> > +++ b/README.md
> > @@ -110,6 +110,19 @@ git format-patch -o proposal1/ HEAD~1..<br>
> >  git send-email --to=virtio-comment@lists.linux.dev proposal1/0001-*
> >  </code>
> >
> > +<dl>Optionally, you can use
> > +<A
> > +HREF="https://github.com/stefanha/git-publish">git-publish</A> to submit a patch. This project already contains a git-publish's profile that will configure some fields, i.e., To field with the right address. After you have installed git-publish, the procedure is the following:
> 
> Nit: remove uppercase and the line split? Also, you could use acute
> accents surrounding the `To` field, to highlight it in the markdown.
> Also, not sure that the genitive is correct there for `git-publish's
> pofile`. And if you want to give an example, better use `e.g.` instead
> of `i.e.`. So all in all, something like this maybe?
> 
> <a href="https://github.com/stefanha/git-publish">git-publish</a> to
> submit a patch. This project already contains a `git-publish` profile
> that will configure some fields, e.g., `To` field with the right
> address. After you have installed `git-publish`, the procedure is the
> following:
> 

Thanks, I'll send v3 with those changes.

Matias