From: peter at colberg.org (Peter Colberg)
Subject: Development Flow Improvements
Date: Thu, 24 Nov 2016 18:23:03 -0500 [thread overview]
Message-ID: <20161124232303.ptr2lvw6vdywrwal@ceyx> (raw)
In-Reply-To: <CAHmME9oN-dpM2zsgcQby3nHukSdA_9LFrzX8WH=5LB11-E2kkA@mail.gmail.com>
Hi Jason,
Thanks for tagging the new release!
On Wed, Sep 28, 2016 at 01:27:38AM +0200, Jason A. Donenfeld wrote:
> zx2c4 at thinkpad ~/Projects/cgit $ git push
> Total 0 (delta 0), reused 0 (delta 0)
> To ssh://git.zx2c4.com/cgit
> ff9893a..11695a5 master -> master
May I suggest a minor improvement to the work flow?
Before pushing to "master" you can simulate pushing for a final review:
# git push -n
# git log -p -c -M --stat --decorate --pretty=fuller ff9893a..11695a5
(I use a git alias "review" for the latter.)
This allows one to catch things like an accidental revert of a submodule.
Peter
prev parent reply other threads:[~2016-11-24 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 18:52 Jason
2016-09-27 21:05 ` jamie.couture
2016-09-27 23:27 ` Jason
2016-09-28 7:16 ` mailings
2016-11-24 23:23 ` peter [this message]
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=20161124232303.ptr2lvw6vdywrwal@ceyx \
--to=cgit@lists.zx2c4.com \
/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;
as well as URLs for NNTP newsgroup(s).