Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: synchronizing with Emacs, take two
Date: Fri, 25 Feb 2011 16:07:28 -0600	[thread overview]
Message-ID: <87k4gn7opr.fsf@lifelogs.com> (raw)
In-Reply-To: <87iq3fimiq.fsf@lifelogs.com>

On Thu, 12 Aug 2010 15:50:05 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> On Fri, 02 Jul 2010 12:57:32 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote: 
KY> Ted Zlatanov wrote:
>>> Then the Bazaar commit message can be just that first line.  If there's
>>> no newline after the first line in our commit message, we'll know the
>>> comitter didn't provide a one-line summary.

KY> Oh, I see.  I learned that that empty line is significant.

TZ> I think it's reasonable.  It should look nice in this format:

TZ> git log --oneline

TZ> e.g.

TZ> ...
TZ> 77a9b0f Minor bug fixes for gnus-sync.el.
TZ> 2a6fa29 Make saving and restoring of hidden threads work with overlays. Patch applied by Ted Zlatanov.
TZ> e1bba25 Add new gnus-sync.el library.
TZ> ...

TZ> That's very handy when you're reviewing changes.

I wanted to give my .gitconfig file in case anyone finds it useful.  The
lg and lg2 aliases in particular can make life easier.  I've collected
them from many places so I can't give credit where it's due.

Ted

[color]
	diff = auto
	status = auto
	branch = auto
	interactive = auto

[alias]
	st = status
	ci = commit
	co = checkout
	staged = "diff --cached"
	unstaged = diff
	both = "diff HEAD"
	oneline = "log --pretty=oneline"
	amend = "commit --ammend"
	am = "commit --ammend"
        lg = "log --graph --all --pretty=format:'%Cred%h%Creset - %Cgreen(%cr)%Creset %s%C(yellow)%d%Creset' --abbrev-commit --date=relative"
        lg2 = "log --oneline --date-order --graph --all --decorate"
	l = pull
	h = push
	hard = "reset --hard HEAD"
	r = "reset HEAD"
        ca = "commit -a"
        aa = "add -A"




      reply	other threads:[~2011-02-25 22:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3zl51tzgl.fsf@fleche.redhat.com>
     [not found] ` <87zl07ynxi.fsf@gate450.dyndns.org>
     [not found]   ` <mailman.7.1273778942.8369.bug-gnu-emacs@gnu.org>
2010-06-30 21:35     ` bug#5284: 23.1; gnus-summary-expire-thread does not work Ted Zlatanov
2010-06-30 21:46       ` synchronizing with Emacs, take two Ted Zlatanov
2010-07-01  2:11         ` Katsumi Yamaoka
2010-07-01  2:34           ` Dave Goldberg
2010-07-01 13:59           ` Ted Zlatanov
2010-07-02  3:57             ` Katsumi Yamaoka
2010-07-04 22:26               ` Mike Kupfer
2010-08-12 20:50               ` Ted Zlatanov
2011-02-25 22:07                 ` Ted Zlatanov [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=87k4gn7opr.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).