From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jon Seymour <jon.seymour@gmail.com>
Cc: "Jakub Narębski" <jnareb@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: RFC: repository of handy git aliases?
Date: Tue, 16 Aug 2011 15:55:51 +0200 [thread overview]
Message-ID: <4E4A76E7.2090100@drmicha.warpmail.net> (raw)
In-Reply-To: <CAH3AnrrNPBNNNr7Lm2-vnqOisxWorF4FS32H+LBaybWF3KdnGg@mail.gmail.com>
Jon Seymour venit, vidit, dixit 08.08.2011 12:43:
> On Mon, Aug 8, 2011 at 8:22 PM, Jon Seymour <jon.seymour@gmail.com> wrote:
>> On Mon, Aug 8, 2011 at 7:45 PM, Jakub Narębski <jnareb@gmail.com> wrote:
>>> On 8/8/11, Jon Seymour <jon.seymour@gmail.com> wrote:
>
> I've also added this...
>
> Listing the tips of branches in pu that are not in master
> ===========================================
>
> Suppose you have two aliases defined like so:
>
> [alias]
> oneline = !/usr/bin/xargs -L1 git log --decorate --max-count=1 --oneline
How about
oneline = git log --no-walk --decorate --oneline
> tips = "!_() { t=$(git rev-list --no-merges --max-count=1
> \"$@\"); if test -n \"$t\"; then echo $t; _ \"$@\" ^$t; fi; }; _"
>
That one is way over my head, but if
> Then:
>
> git tips origin/pu ^origin/next | git oneline
is your typical use case you may like
git branch --merged origin/pu --contains origin/next
(or with --no-merged, but put it first.)
> might show something like this:
>
> 9dcca58 filter-branch.sh: de-dent usage string
> 704c335 On Cygwin support both UNIX and DOS style path-names
> 1c460f9 t3030: fix accidental success in symlink rename
> 9e81372 test-path-utils: Add subcommand "prefix_path"
> ad733bd revert: Propagate errors upwards from do_pick_commit
> 76cf946 fixup! xdiff/xhistogram: rework handling of recursed results
> df6a9c7 fixup! describe: Refresh the index when run with --dirty
> c9f57a0 squash! ls-files: fix pathspec display on error
> a1288bc add--interactive: add option to autosplit hunks
> 365b78a t5800: point out that deleting branches does not work
> c997182 limit "contains" traversals based on commit generation
> 914b6fb doc/fast-import: document feature import-marks-if-exists
> b792c06 branch -v: honor core.abbrev
> b166408 mergetool: Don't assume paths are unmerged
> b29d76f merge: mark the final "Merge made by..." message for l10n
> 942cf39 receive-pack: Allow server to refuse pushes with too many objects
>
> which is a list of the tips of branches that are in pu, but not in next.
That's not quite the standard --decorate, is it? ;)
Michael
next prev parent reply other threads:[~2011-08-16 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 4:46 RFC: repository of handy git aliases? Jon Seymour
2011-08-08 9:45 ` Jakub Narębski
2011-08-08 10:22 ` Jon Seymour
2011-08-08 10:43 ` Jon Seymour
2011-08-08 10:45 ` Jon Seymour
2011-08-16 13:55 ` Michael J Gruber [this message]
2011-08-18 14:52 ` Jon Seymour
2011-08-18 15:40 ` Michael J Gruber
2011-08-19 6:15 ` Jon Seymour
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=4E4A76E7.2090100@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=jon.seymour@gmail.com \
/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).