From: "Shawn O. Pearce" <spearce@spearce.org>
To: Lars Hjemli <hjemli@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] checkout: allow full refnames for local branches
Date: Wed, 9 May 2007 16:11:05 -0400 [thread overview]
Message-ID: <20070509201105.GF3141@spearce.org> (raw)
In-Reply-To: <8c5c35580705091301s19dcd2e0q20a4c84e3dd23d82@mail.gmail.com>
Lars Hjemli <hjemli@gmail.com> wrote:
> On 5/9/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> >If you are building "porcelain" to sit over Git and offer up a pretty
> >view of things, I would encourage you to avoid the stock porcelain.
> >Don't use git-checkout, its stock porcelain. Instead go right to
> >the plumbing. The plumbing doesn't really change behavior as often
> >(if ever).
>
> Thanks, I probably will (also to avoid the shell scripts, since my
> porcelain is aimed at my co-workers who are stuck on windows)
Are you building a strictly Win32 native GUI? Or something else?
Can I ask what sort of features you are going after? (And if
there's a git repository available, feel free to just point me at
it and ignore my questions.)
I'm just curious. We seem to have a lot of user interface projects
going on at once right now (Eclipse plugin, git-gui, gitk, qgit, tig,
gitweb, blameview) and everyone's been learning from each other.
I think the competition is good, there's no clear right way to do
things here. As the primary author of git-gui, I do want to try
and keep current with what the others are up to. ;-)
--
Shawn.
next prev parent reply other threads:[~2007-05-09 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 8:40 [PATCH] checkout: allow full refnames for local branches Lars Hjemli
2007-05-09 8:48 ` Junio C Hamano
2007-05-09 9:07 ` Lars Hjemli
2007-05-09 18:54 ` Shawn O. Pearce
2007-05-09 20:01 ` Lars Hjemli
2007-05-09 20:11 ` Shawn O. Pearce [this message]
2007-05-09 20:38 ` Lars Hjemli
2007-05-09 19:37 ` Junio C Hamano
2007-05-09 19:55 ` Lars Hjemli
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=20070509201105.GF3141@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
--cc=junkio@cox.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 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.