From: Jon Seymour <jon.seymour@gmail.com>
To: git@vger.kernel.org
Cc: Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Add support for author-oriented git-rev-list switches [rev 9]
Date: Fri, 10 Jun 2005 09:10:42 +1000 [thread overview]
Message-ID: <2cfc4032050609161059a0f0c@mail.gmail.com> (raw)
In-Reply-To: <2cfc4032050609085341e46242@mail.gmail.com>
[rev 9]
* oops, missed some whitespace in my commit.c edits - begone,
whitespace, begone!
* slight change to semantics of --prune-at-author - now includes the
author's own commits
but prunes the parents of the author's own changes. This helps put the
cut points into some kind of context when the author has contributions
in multiple branches.
As before available from:
http://blackcubes.dyndns.org/epoch/wrt-patch-latest.patch
If anyone has objections to the changed semantics, let's discuss.
jon.
prev parent reply other threads:[~2005-06-09 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 9:01 [PATCH] Add support for author-oriented git-rev-list switches [rev 6] Jon Seymour
2005-06-09 9:37 ` Jon Seymour
2005-06-09 15:53 ` [PATCH] Add support for author-oriented git-rev-list switches [rev 8] Jon Seymour
2005-06-09 20:35 ` Junio C Hamano
2005-06-09 23:10 ` Jon Seymour [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=2cfc4032050609161059a0f0c@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=jon@blackcubes.dyndns.org \
--cc=torvalds@osdl.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 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.