All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Petr Baudis <pasky@suse.cz>, Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: Documentation (mainly user-manual) patches
Date: Sat, 19 May 2007 00:02:12 -0400	[thread overview]
Message-ID: <20070519040212.GC3141@spearce.org> (raw)
In-Reply-To: <20070518134316.GA21925@fieldses.org>

"J. Bruce Fields" <bfields@fieldses.org> wrote:
> On Fri, May 18, 2007 at 06:56:35AM +0200, Petr Baudis wrote:
> >   BTW, there is this nice git-request-pull tool which will prepare this
> > mail for you and additionally include the list of commits included in
> > that repository, which is somewhat more friendly to the readers (I
> > myself wondered). ;-)
> 
> OK!  I'll start including the shortlog.  Appended, if anyone's still
> curious about this one.--b.

request-pull also does nice things like include the fetch URL, and
the branch name, and in a nice format that makes it very easy to
copy and paste into a "git pull" (or "git fetch") command line[*1*],
so its slightly more than just the shortlog.  ;-)


[*1*] By popular demand from Git's creator.

-- 
Shawn.

  reply	other threads:[~2007-05-19  4:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18  3:37 Documentation (mainly user-manual) patches J. Bruce Fields
2007-05-18  3:39 ` [PATCH] user-manual: reorganize public git repo discussion J. Bruce Fields
2007-05-18  4:56 ` Documentation (mainly user-manual) patches Petr Baudis
2007-05-18 13:43   ` J. Bruce Fields
2007-05-19  4:02     ` Shawn O. Pearce [this message]
2007-05-19  4:13       ` J. Bruce Fields
2007-05-19  4:32         ` Shawn O. Pearce
2007-05-19  5:19           ` J. Bruce Fields

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=20070519040212.GC3141@spearce.org \
    --to=spearce@spearce.org \
    --cc=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=pasky@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.