public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses•org>
To: "Shawn O. Pearce" <spearce@spearce•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:13:57 -0400	[thread overview]
Message-ID: <20070519041357.GA2679@fieldses.org> (raw)
In-Reply-To: <20070519040212.GC3141@spearce.org>

On Sat, May 19, 2007 at 12:02:12AM -0400, Shawn O. Pearce wrote:
> 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.  ;-)

I know, but that's not hard to do by hand.  Which doesn't, of course,
mean I won't screw it up....

But, actually, I tried it just now and it only gave the url:

	The following changes since commit 164b19893ab5bc66b531a26480149a0dff082969:
	  Michael Hendricks (1):
		Document core.excludesfile for git-add

	are found in the git repository at:

		git://linux-nfs.org/~bfields/git.git

How's it supposed to figure out the branch name?  (And I'm not sure
about that "change since commit..." stuff--that seems like slight
overkill.)

--b.

  reply	other threads:[~2007-05-19  4:14 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
2007-05-19  4:13       ` J. Bruce Fields [this message]
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=20070519041357.GA2679@fieldses.org \
    --to=bfields@fieldses$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    --cc=junkio@cox$(echo .)net \
    --cc=pasky@suse$(echo .)cz \
    --cc=spearce@spearce$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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