From: Matthew L Foster <mfoster167@yahoo.com>
To: Rogan Dawes <lists@dawes.za.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: merge time
Date: Mon, 30 Jul 2007 10:06:59 -0700 (PDT) [thread overview]
Message-ID: <28948.8052.qm@web51002.mail.re2.yahoo.com> (raw)
In-Reply-To: <46AE1100.2020005@dawes.za.net>
--- Rogan Dawes <lists@dawes.za.net> wrote:
> And also keep in mind that on the command line you can invoke a lot of
> "plumbing commands" that you certainly wouldn't expect to be exposed in
> a web interface.
If the web interface requires logins over https why can't plumbing commands be exposed to the web?
Though I agree not everything needs to be webified. What I envision is a wikipedia style interface
front end with git remaining the backend so you can more easily browse the file system and see
history and diff the way you can on Wikipedia. But that idea is very separate from my concern that
right now gitweb.cgi effectively has a bug in it because it sorts using external/superset commit
order/time rather than local commit order which causes changes to appear as if they were made
before they were really merged locally.
-Matt
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
next prev parent reply other threads:[~2007-07-30 17:07 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 17:33 merge time Matthew L Foster
2007-07-29 23:19 ` Jakub Narebski
2007-07-29 23:35 ` Linus Torvalds
2007-07-30 1:11 ` Matthew L Foster
2007-07-30 1:27 ` david
2007-07-30 2:29 ` Linus Torvalds
2007-07-30 2:43 ` Matthew L Foster
2007-07-30 3:06 ` Linus Torvalds
2007-07-30 3:16 ` Linus Torvalds
2007-07-30 4:13 ` Matthew L Foster
2007-07-30 11:33 ` Sean
2007-07-30 3:57 ` Matthew L Foster
2007-07-30 6:10 ` Steffen Prohaska
2007-07-30 6:48 ` Junio C Hamano
2007-07-30 7:44 ` Steffen Prohaska
2007-07-30 7:49 ` Shawn O. Pearce
2007-07-30 8:09 ` Steffen Prohaska
2007-07-30 8:14 ` Jeff King
2007-07-30 8:24 ` Junio C Hamano
2007-07-30 8:31 ` Jeff King
2007-07-30 8:25 ` Steffen Prohaska
2007-07-30 8:32 ` Jeff King
2007-07-30 8:34 ` david
2007-07-30 8:41 ` Jeff King
2007-07-30 17:42 ` Linus Torvalds
2007-07-31 18:06 ` Steffen Prohaska
2007-07-31 20:07 ` david
2007-07-30 12:44 ` Rogan Dawes
2007-07-30 16:14 ` Matthew L Foster
2007-07-30 16:20 ` Johannes Schindelin
2007-07-30 16:24 ` Matthew L Foster
2007-07-30 16:25 ` Rogan Dawes
2007-07-30 17:06 ` Matthew L Foster [this message]
2007-07-30 17:13 ` david
2007-07-30 21:57 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2007-07-30 2:28 Matthew L Foster
2007-07-30 3:09 ` Linus Torvalds
2007-07-30 4:10 ` Matthew L Foster
2007-07-30 4:17 ` david
2007-07-30 16:20 ` Matthew L Foster
2007-07-30 16:23 ` david
2007-07-30 17:11 ` Matthew L Foster
2007-07-30 17:33 ` david
2007-07-30 22:11 ` Robin Rosenberg
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=28948.8052.qm@web51002.mail.re2.yahoo.com \
--to=mfoster167@yahoo.com \
--cc=git@vger.kernel.org \
--cc=lists@dawes.za.net \
/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).