mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: Thorsten Scherer <thorsten.scherer@eckelmann.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2 1/5] ptxdist: add host autotools macro archive for tpm2
Date: Mon, 18 Mar 2019 09:51:24 +0100	[thread overview]
Message-ID: <20190318085124.tack5wj6pp7n7cdr@pengutronix.de> (raw)
In-Reply-To: <20190315150902.GA6173@ws067.eckelmann.group>

Hi Thorsten,

On Fri, Mar 15, 2019 at 04:09:02PM +0100, Thorsten Scherer wrote:
> thank you for your explanations.  I will follow them in the next
> version of the patchset.
> 
> Maybe you could help me with some additional questions.
> 
> - As this patchset is a little old, would it be better to keep the
>   versions of the libraries as they are and bump them after the
>   patchset got applied (if it will be) or should they be bumped with the
>   next set of patches.
> 
> - Would it make sense to break the patchset up into single patches?

In general I think it's better to make smaller, atomic commits, than
larger commits that do too much at once, and which are then harder to
review. So I would tend tomake one commit for the version bump and then
the other things.

 - Roland

-- 
Roland Hieber                     | r.hieber@pengutronix.de     |
Pengutronix e.K.                  | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2019-03-18  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 10:49 [ptxdist] [PATCH v2 0/5] add packages for tpm Thorsten K. Scherer
2018-12-17 10:49 ` [ptxdist] [PATCH v2 1/5] ptxdist: add host autotools macro archive for tpm2 Thorsten K. Scherer
     [not found]   ` <20181230033939.3mawbfpfgv5ab5vb@pengutronix.de>
     [not found]     ` <20190315150902.GA6173@ws067.eckelmann.group>
2019-03-18  8:51       ` Roland Hieber [this message]
2018-12-17 10:49 ` [ptxdist] [PATCH v2 2/5] ptxdist: add tpm2-abrmd 2.0.3 Thorsten K. Scherer
2018-12-17 10:49 ` [ptxdist] [PATCH v2 3/5] ptxdist: add tpm2-tss version 2.1.0 Thorsten K. Scherer
2018-12-17 10:50 ` [ptxdist] [PATCH v2 4/5] ptxdist: add tpm2-tools 3.1.3 Thorsten K. Scherer
2018-12-17 10:50 ` [ptxdist] [PATCH v2 5/5] ptxdist: add tpm2-tss-engine c9061a7 Thorsten K. Scherer
2018-12-20 14:56 ` [ptxdist] [PATCH v2 0/5] add packages for tpm Scherer, Thorsten

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190318085124.tack5wj6pp7n7cdr@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=thorsten.scherer@eckelmann.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox