Re: [PATCH 0/2] Add --dry-run option to git-push

From: Lars Hjemli <hjemli@gmail.com>
Date: Oct 11, 2007, 07:57 UTC
Message-ID: <8c5c35580710110057r29c1fe0w7f9e2825fa33@mail.gmail.com>
In-Reply-To: <2faad3050710101634s5ed39bcbn723184810bc265d5@mail.gmail.com>

On 10/11/07, Baz <brian.ewins@gmail.com> wrote:

Show 9 quoted lines

> there was discussion recently about the default behaviour of git-push
> having the potential to confuse, making it easy to push commits that
> are still cooking in other branches.
>
> Its also possible for newbies to make mistakes with refspecs, but
> there's no way to know if you've got the syntax right without actually
> pushing. Steffan suggested a dry-run flag, which I've always wanted
> too, so here's an attempt. Patches git-send-pack, git-push, their
> docs, and adds a test for git-push.

Maybe some of this description could be reused in the commit messages?

> first patch to the list and the mailer will
> probably mangle it (sigh)

Yeah, it did.

Would it be possible for you to resend with git-send-email after adding proper commit messages? If git-send-email is not an option, attaching the patches are preferable to the current mangling.

-- larsh