Re: [PATCH] ls-tree: make <tree-ish> optional
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Jul 4, 2018, 09:38 UTC
- Message-ID
- <CAPig+cR4=0r5qRmKzV7Tzph49Ln0kJDAGtSMxF0BNxujwjeiWg@mail.gmail.com>
- In-Reply-To
- <368608dc-4351-541c-0236-9f5760ca5d97@gmail.com>
On Tue, Jul 3, 2018 at 8:05 PM Joshua Nelson <jyn514@gmail.com> wrote:
> Is it customary to send a new patch or second patch that builds on the > first?
It depends what you mean. If there were problems with a version of a patch you sent, then you "re-roll", which means you re-send the patch in its entirety as if it's brand new (not building on the problematic previous version). You'd also indicate the attempt number in the subject; for instance "[PATCH v2]" for the second attempt.
If you're working on some functionality that is built up over a series steps, then you would send all those patches as a "patch series", in which each patch in the series builds upon the patch or patches preceding it in the series.
> If I specify a commit range to git-send-email it sends both, not > just the latest.
I'm not quite sure what you mean.