All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] git init: optionally allow a directory argument
Date: Sat, 25 Jul 2009 13:13:09 +1000	[thread overview]
Message-ID: <87r5w5h2uy.fsf@rimspace.net> (raw)
In-Reply-To: 7vab2t64cg.fsf@alter.siamese.dyndns.org

Junio C Hamano <gitster@pobox.com> writes:
> Nanako Shiraishi <nanako3@lavabit.com> writes:
>
>> When starting a new repository, I see my students often say
>>     % git init newrepo
>> and curse git.  They could say
>>     % mkdir newrepo; cd newrepo; git init
>> but allowing it as an obvious short-cut may be nicer.
>>
>> Signed-off-by: Nanako Shiraishi <nanako3@lavabit.com>
>
> Hmm, I didn't realize this is so common a wish among new people.  The patch
> seems clean.  Anybody has comments, both on code and the use case?

It still surprises me that git doesn't do this, since it is at odds with
almost every other version control system I have on hand or experience with,
other than CVS; Subversion, svk, Bazaar and Mercurial all take a trailing
target argument.

CVS and monotone take an option to specify where; only darcs is like git and
uses the current directory as the target.

So, from where I sit it makes sense to have 'git init foo' create a 'foo'
directory and repository below the current location.

Regards,
        Daniel

...and, yeah, I still get caught every now and then when I create a new
repository by hand.
-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

  reply	other threads:[~2009-07-25  3:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 21:59 [PATCH] git init: optionally allow a directory argument Nanako Shiraishi
2009-07-24 23:36 ` Junio C Hamano
2009-07-25  3:13   ` Daniel Pittman [this message]
2009-07-25  6:41   ` Alex Scarborough
2009-07-25  6:41 ` Junio C Hamano
2009-07-25  7:45   ` Johannes Sixt
2009-07-25  9:26     ` Junio C Hamano

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=87r5w5h2uy.fsf@rimspace.net \
    --to=daniel@rimspace.net \
    --cc=git@vger.kernel.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.
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.