public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Commit Policy
Date: Wed, 15 Jan 2014 02:19:08 +0000	[thread overview]
Message-ID: <20140115021908.GA4125@woodpecker.gentoo.org> (raw)
In-Reply-To: <1389598174.14760.8.camel@big_daddy.dol-sen.ca>

On Sun, Jan 12, 2014 at 11:29:34PM -0800, Brian Dolbec wrote:
> On Mon, 2014-01-13 at 07:43 +0100, Sebastian Luther wrote:
> > 
> > One more useful thing:
> > 
> > Put this in ~/.gitconfig:
> > [color]
> > 	ui = auto
> > 
> > This way git diff will use colors, including highlighting of trailing
> > whitespace.
> > 
> > 
> > 
> 
> I use an editor that I have set for both showing whitespace (you see
> tabs, spaces) and auto-strips trailing whitespace on save.
> 
> nice tip for the git diff.
> 
> I like using dev-vcs/gitg for doing commits, viewing different branch
> trees, cherry-picking (in color too).  For commits it lets you pick
> changes 1 at a time (+ or -) when you've done several changes, but wish
> to split them into logical commits.  Handy when you spot things that
> need fixing, but don't want to forget to do after your current change
> session & commit.
Hope I'm not making too much noise here ;-)
if you want to amend your git commits a lot,
saying, movie commits up/down, merge/split them
you could try dev-vcs/stgit, it's my favorite!
> 
> -- 
> Brian Dolbec <dolsen@gentoo.org>

Lan


  reply	other threads:[~2014-01-15  2:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 10:35 [gentoo-portage-dev] Commit Policy Brian Dolbec
2014-01-10 17:24 ` Matthew Thode
2014-01-10 18:13 ` Pavel Kazakov
2014-01-11  3:01 ` Alexander Berntsen
2014-01-13  6:43 ` Sebastian Luther
2014-01-13  7:29   ` Brian Dolbec
2014-01-15  2:19     ` Yixun Lan [this message]
2014-01-13 16:37   ` [gentoo-portage-dev] " W. Trevor King
2014-01-15  3:22   ` [gentoo-portage-dev] " Tom Wijsman
2014-01-15  8:42     ` Alexander Berntsen
2014-01-15  3:17 ` Tom Wijsman

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=20140115021908.GA4125@woodpecker.gentoo.org \
    --to=dlan@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /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