From: Junio C Hamano <gitster@pobox.com>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: "Petr Baudis" <pasky@suse.cz>,
git@vger.kernel.org, jnareb@gmail.com, ltuikov@yahoo.com
Subject: Re: [ANNOUNCE] git/gitweb.git repository
Date: Sat, 01 Sep 2007 10:54:04 -0700 [thread overview]
Message-ID: <7vwsvas24j.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <9e4733910709010815t23849056j9039a9d92eae15ee@mail.gmail.com> (Jon Smirl's message of "Sat, 1 Sep 2007 11:15:58 -0400")
"Jon Smirl" <jonsmirl@gmail.com> writes:
> On 8/30/07, Petr Baudis <pasky@suse.cz> wrote:
>>
>> due to popular (Junio's) demand, I have set up a gitweb-oriented fork
>> of git at repo.or.cz:
>>
>> http://repo.or.cz/w/git/gitweb.git
>>
>> It is meant as a hub for various gitweb-related patches and
>> development efforts. So far it is pre-seeded by the patches repo.or.cz's
>> gitweb uses. It is divided to three main branches (StGIT patchstacks in
>> reality), where master is what Junio is gonna pull to git's master.
>
> Using gitweb....
> Since this is a patch stack, how do I get the summary log messages for
> just the commits on the branch without getting the log messages for
> the master repository mixed in? Would that give me a nice list of the
> pending patches?
That's an excellent suggestion. I'd love to see "fork" aware
gitweb myself.
If a project A is "forked" repo.or.cz style to a project B, what
often is interesting to see is what changes B has relative to A.
In other words, you would want to view all of B except what are
in A, something like:
$ gitk --all --not $(git for-each-ref --format='%(objectname)' refs/remotes/A)
next prev parent reply other threads:[~2007-09-01 17:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 0:01 [ANNOUNCE] git/gitweb.git repository Petr Baudis
2007-08-31 0:56 ` David Symonds
2007-08-31 1:00 ` David Symonds
2007-09-01 5:46 ` David Symonds
2007-09-07 6:39 ` David Symonds
2007-09-01 1:06 ` Luben Tuikov
2007-09-01 1:16 ` Petr Baudis
2007-09-01 1:23 ` Luben Tuikov
2007-09-01 1:25 ` Johannes Schindelin
2007-09-01 1:31 ` Petr Baudis
2007-09-01 1:44 ` Junio C Hamano
2007-09-01 2:15 ` Luben Tuikov
2007-09-01 4:57 ` Junio C Hamano
2007-09-01 2:06 ` Luben Tuikov
2007-09-01 15:15 ` Jon Smirl
2007-09-01 17:54 ` Junio C Hamano [this message]
2007-09-01 17:54 ` Jakub Narebski
2007-09-04 5:42 ` Junio C Hamano
2007-09-04 5:47 ` Adam Roben
2007-09-04 5:50 ` Shawn O. Pearce
2007-09-04 8:19 ` Junio C Hamano
2007-09-04 5:58 ` Andreas Ericsson
2007-09-04 9:38 ` Petr Baudis
2007-09-04 7:56 ` Luben Tuikov
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=7vwsvas24j.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=jonsmirl@gmail.com \
--cc=ltuikov@yahoo.com \
--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.