git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kyle Moffett <kyle@moffetthome.net>
To: Hannu Koivisto <azure@iki.fi>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 1/2] user-manual: Simplify the user configuration.
Date: Sun, 25 Jan 2009 02:32:38 -0500	[thread overview]
Message-ID: <f73f7ab80901242332x7de1f856j51181c3c05cf2b11@mail.gmail.com> (raw)
In-Reply-To: <83wscndv57.fsf@kalahari.s2.org>

On Thu, Jan 22, 2009 at 1:59 PM, Hannu Koivisto <azure@iki.fi> wrote:
> In any case, what Cygwin git does should be expected by Cygwin
> users.  If msysgit wanted to be a really native Windows application
> and store the configuration where Microsoft thinks it should be
> stored, it probably shouldn't store the config under "home
> directory" to begin with (I'm guessing that's what it does) but
> under %USERPROFILE\Application Data\Git (...FILE\Local
> Settings\... in case non-roaming storage is wanted).  And in that
> case the manual might be misleading for msysgit users.  See
> e.g. <http://msdn.microsoft.com/en-us/library/ms995853.aspx>.

Actually, if msysgit really wanted to be a "native" windows program,
it would use the good-old brain-damaged method of storing
everything-and-the-kitchen-sink in the registry, including the
locations and reflogs for every repository you have ever examined.
Admittedly the collection of 150+ dotfiles in my Linux homedir looks
relatively similar to parts of the windows registry at times...

Cheers,
Kyle Moffett

  parent reply	other threads:[~2009-01-25  7:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 18:09 [PATCH 1/2] user-manual: Simplify the user configuration Felipe Contreras
2009-01-21 18:09 ` [PATCH 2/2] Fix typo Felipe Contreras
2009-01-21 18:55 ` [PATCH 1/2] user-manual: Simplify the user configuration Markus Heidelberg
2009-01-21 19:04   ` [PATCH] " Felipe Contreras
2009-01-21 19:18     ` Jeff King
2009-01-21 19:39       ` Felipe Contreras
2009-01-21 19:51         ` Jeff King
2009-01-21 20:54 ` [PATCH 1/2] " Junio C Hamano
2009-01-21 21:13   ` Wincent Colaiuta
2009-01-21 21:19   ` Felipe Contreras
2009-01-22 16:17     ` Hannu Koivisto
2009-01-22 16:57       ` Felipe Contreras
2009-01-22 17:14         ` Junio C Hamano
2009-01-22 17:28           ` Johannes Schindelin
2009-01-22 18:59         ` Hannu Koivisto
2009-01-24  8:21           ` Felipe Contreras
2009-01-24 13:42             ` Johannes Schindelin
2009-01-24 14:04               ` Felipe Contreras
2009-01-25 20:34                 ` Junio C Hamano
2009-01-25 21:12                   ` Felipe Contreras
2009-01-25 21:44                     ` Jeff King
2009-01-25 22:55                       ` Wincent Colaiuta
2009-01-25 23:20                         ` Jeff King
2009-01-25  7:32           ` Kyle Moffett [this message]
2009-01-25 12:06             ` Johannes Schindelin

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=f73f7ab80901242332x7de1f856j51181c3c05cf2b11@mail.gmail.com \
    --to=kyle@moffetthome.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=azure@iki.fi \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).