git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Elijah Newren <newren@gmail.com>, git@vger.kernel.org
Subject: Re: Which freedesktop.org "design flaws" in git are still relevant?
Date: Fri, 29 Feb 2008 22:16:29 +0100	[thread overview]
Message-ID: <200802292216.29788.jnareb@gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802291551310.4911@xanadu.home>

On Fri, 29 Feb 2008, Nicolas Pitre wrote:
> On Fri, 29 Feb 2008, Elijah Newren wrote:
> 
>> The page http://www.freedesktop.org/wiki/Infrastructure/git/UIFlaws
>> contains a number of claimed UI flaws of git.  I suspect that a number
>> of them are out-of-date; it doesn't seem to jive with my recent
>> reading of the documentation.  Could anyone point out which are still
>> accurate with recent git, and which aren't?
> 
> It says:
> 
> 	Infrastructure/git/UIFlaws (last edited 2007-06-03 18:41:26 by 
> 	JakubNarebski) 
> 
> and despite being updated almost 9 months ago, the content feels even 
> older than that.
> 
> Jakub?

http://www.freedesktop.org/wiki/Infrastructure/git/UIFlaws?action=info

I have just fixed one error there, and didn't take time to correct
all the things.

P.S. I have replied in another message in this thread, discussion those
mentioned "flaws" one by one.
-- 
Jakub Narebski
Poland

  reply	other threads:[~2008-02-29 21:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 20:32 Which freedesktop.org "design flaws" in git are still relevant? Elijah Newren
2008-02-29 20:56 ` Nicolas Pitre
2008-02-29 21:16   ` Jakub Narebski [this message]
2008-02-29 21:11 ` Jakub Narebski
2008-02-29 21:50   ` Junio C Hamano
2008-02-29 21:58   ` Daniel Barkalow
2008-02-29 22:40     ` Jay Soffian
2008-02-29 22:52       ` Jay Soffian
2008-02-29 22:58       ` Daniel Barkalow

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200802292216.29788.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    --cc=nico@cam.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).