On Wed, Jun 11, 2014 at 10:05:46AM +0200, Fabian Ruch wrote:
> Hi Michael,
> On 05/18/2014 11:17 PM, Michael S. Tsirkin wrote:
> > As a maintainer, I often get patches by mail, then
> > acked-by,reviewed-by etc responses are sent by separate
> > mail.
> > 
> > I like making acks commits,
> > this way they are easy to keep track of
> > as part of git history.
> In order to fully understand your additions, I think, I need some
> clarification on the term "ack commit".

I think the two additions should be judged separately, they aren't

So I am not sure we need to spend time discussing
what is an ack commit.

What I mean is that I prefer using git history for
recording activity, and git rebase for modifying
I think I am not alone in this.

To record acks, I wrote this tool to
create empty commits, that only record log
changes. They are named specially such that
rebase knows not to discard them, and to
automate the editing stage.

I added some features to the tool since.
Did not yet address all comments I got here, but just in case
you are curious it's attached at the end.

> What is an ack commit exactly?
> Suppose our principal commit has the commit message
>     Some changes
>     The changes are...
>     Signed-off-by: A U Thor <aut...@example.com>
> and we receive an email from Somebody saying
>     > Some changes
>     >
>     > The changes are...
>     >
>     > Signed-off-by: A U Thor <aut...@example.com>
>     Reviewed-by: Somebody <someb...@example.com>

Other possible cases I handle:
    people reply with:

    For the series:
        Reviewed-by: Somebody <someb...@example.com>

This uses the save/restore flags.

or an informal
    Ack the series
(this one I handle by creating ACKS file manually,
 then applying it with git ack restore)

Someone sends a fixup! patch, and someone else
replies to the fixup with Reviewed-by: tag.
(this was not handled correctly in the version
you reviewed, I attach latest one below where it is
handled correctly).

> . Now, if I understand correctly, we create an empty commit on top of
> the principal commit using the following commit message.
>     Some changes
>     Reviewed-by: Somebody <someb...@example.com>
> Is this commit then called an ack commit?

git ack creates commits like this:

ack! Some changes

Reviewed-by: Somebody <someb...@example.com>

Other work-flows

> Can an ack commit be non-empty?

At the moment git ack does not create non empty commits.

> Is a commit still an ack if its description mentions additional text
> between the subject and the tag lines?

At the moment git ack does not create such commits.

> Maybe the ack command for todo lists and ack commits have little to do
> with one another.

I use them together but ack command is more powerful than git ack.
Same as commit --fixup, that is not the only way to
use fixup!.

> If we stick to the term "ack commit", then the command
> name suggests that it takes the tags from some commit b and appends them
> to the list of tags in the previous commit's (a) message:
>     pick a A commit
>     ack  b The next commit
> However, this obviously does not work by just appending messages. For
> instance, there could be additional text before or after some tag line
> in either commit message. If we treat the workflow you described as a
> very specific use case of the ack command instead, it seems reasonable
> to add such a todo list functionality for melding commits by silently
> appending messages. However, we might consider parametrizing a single
> squash command instead of defining just another name that one has to
> keep in mind for melding commits:

Hmm, I don't see why is flag any easier to remember than a separate command
frankly, and there's help text at the end to remind you.

>     pick             a A commit
>     squash --no-edit b The next commit

That's too much typing I think, I just want to use a
single letter.
You could argue the same thing for fixup right?
It's really squash but discards the log, and there
is no requirement that it fixes anything, it can
add functionality or whatever.
So why not
squash --discardlog b The next commit

I think that would be bad usability, and so would --no-edit.

--no-edit also does not convey the fact that it allows
empty commits.

I don't mind renaming the command to something else
but I could not come up with a better name so far.

> > Since response mail happens to have appropriate
> > subject matching the patch, it's a natural fit to
> > then use git rebase mechanics if we want to smash
> > these acks into the original commit.
> > 
> > I have been using these patches without any problems
> > for a while now, and find the approach very convenient.
> > 
> > Included:
> >     rebase: new ack! action to handle ack commits
> >             this part seems ready for merge to me,
> >             please review and comment
> > 
> >     git-ack: new tool to record an ack
> >             this does not have proper documentation
> >             and tests yet, I definitely intend to
> >             do this but wanted to see whether people
> >             like the UI first.
> >             posting for early review and feedback
> > 
> > [..]
> Thanks for your time,
>    Fabian

## latest git-ack
## changes: handle fixup!/squash!/ack! messages in mail

info=`git mailinfo $msg $patch`
subj=`echo "$info"|sed -n 's/^Subject: //p'`
#strip ack!/fixup!/squash! prefix
subj=`echo "$subj"|sed "s/^fixup![      ]*//"`
subj=`echo "$subj"|sed "s/^squash![     ]*//"`
subj=`echo "$subj"|sed "s/^ack![        ]*//"`
author=`echo "$info"|sed -n 's/^Author: //p'`
email=`echo "$info"|sed -n 's/^Email: //p'`
auth="$author <$email>"
date=`echo "$info"|sed -n 's/^Date: //p'`
echo "ack! $subj" > $sign
echo "" >> $sign
    git diff --cached HEAD
    nop < /dev/null
    echo "DIFF in cache. Not acked, reset or commit!"
    exit 1

usage () {
        echo "Usage: git ack " \
            "[-s|--save|-a|--append|-r|--restore |-c|--clear]\n" >& 2;
        exit 1;


while test $# != 0
        case "$1" in
                usage ;;

    test "$clear"
    rm -f "${GIT_DIR}/ACKS"

    test "$save"
        test "$append"
        cat $msg >> "${GIT_DIR}/ACKS"
        cat $msg > "${GIT_DIR}/ACKS"

    test "$restore"

echo $msg > /dev/tty
    grep '^[A-Z][A-Za-z-]*-by:' $msg >> $sign
    git commit --allow-empty -F $sign --author="$auth" --date="$date"
    echo "No signature found!"
    exit 2
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to